<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<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: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";}
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";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Times New Roman","serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Colleagues, <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'>I am still working through the Charter. Regarding solidarity
though, I suggest that we rephrase the language to ensure that when a member is
representing the BC that they are faithful to approved BC positions.. I am not
sure that we need the more in-depth language.<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'>Thanks,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>David<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"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b>On Behalf Of </b>Zahid
Jamil<br>
<b>Sent:</b> Monday, October 26, 2009 6:54 PM<br>
<b>To:</b> 'Deutsch, Sarah B'; 'Marilyn Cade'; 'Philip Sheppard'; 'bc - GNSO
list'<br>
<b>Subject:</b> RE: [bc-gnso] BC charter v19<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;color:#1F497D'>I
would like to propose some alternative language in regards the following:<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><b><span lang=EN-GB>7.5. Solidarity<o:p></o:p></span></b></p>
<p class=MsoNormal><span lang=EN-GB>Whenever a member speaks publicly within or
to the ICANN community meetings and indicates to others that they are a
Constituency member, it is likely that their view, statement or conduct may be
interpreted by the ICANN community to be a Constituency approved position. As
such, members are expected, when communicating on such occasions to ensure that
their statement(s) and conduct do not undermine, prejudice or detract from an
approved Constituency position(s). This will not affect a member’s right to
communicate their own view, if distinct from an approved Constituency
position(s) by clarifying that such a statement may differ from and does not
reflect the approved Constituency position. Members of the Executive Committee
are required to support approved constituency positions at all times. Both
Members and Executive Committee Members may communicate dissent to a
Constituency position providing they make it clear they are communicating in
their personal capacity.<span style='color:#1F497D'><o:p></o:p></span></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal><b><span lang=EN-GB>10. Privacy of personal data<o:p></o:p></span></b></p>
<p class=MsoNormal><span lang=EN-GB>The Executive Committee, Secretariat,
committees and members of the Constituency will ensure privacy of member’s
and/or their representatives’ personal or personally identifiable data, and in
particular shall not deal with such data in a manner beyond what is necessary
for the purposes for which it was originally collected. Members may also
decide to make such additional aspects of their data available for disclosure
and may consent to any such disclosure by waiving such privacy requirements.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB>[Maybe we could list/identify what sort of
data we are targeting even if don’t necessarily put it into the draft it may
help with explaining to all us members what we mean.]<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'>Sincerely,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'>Zahid Jamil<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:#1F497D'>Barrister-at-law<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'>Jamil &
Jamil<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'>Barristers-at-law<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:#1F497D'>219-221 Central Hotel
Annexe<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:#1F497D'>Merewether Road,
Karachi. Pakistan<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:#1F497D'>Cell:
+923008238230<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:#1F497D'>Tel: +92 21
5680760 / 5685276 / 5655025<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:#1F497D'>Fax: +92 21
5655026<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a href="http://www.jamilandjamil.com/"><span lang=EN-US
style='font-size:9.0pt;font-family:"Times New Roman","serif"'>www.jamilandjamil.com</span></a></span><span
style='font-size:9.0pt;color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.5pt;color:#1F497D'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:7.0pt;color:#1F497D'>Notice /
Disclaimer<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:7.0pt;color:#1F497D'>This message
contains confidential information and its contents are being communicated only
for the intended recipients . If you are not the intended recipient you should
not disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this message by mistake and delete
it from your system. The contents above may contain/are the intellectual
property of Jamil & Jamil, Barristers-at-Law, and constitute privileged
information protected by attorney client privilege. The reproduction, publication,
use, amendment, modification of any kind whatsoever of any part or parts
(including photocopying or storing it in any medium by electronic means whether
or not transiently or incidentally or some other use of this communication)
without prior written permission and consent of Jamil & Jamil is
prohibited.<o:p></o:p></span></p>
</div>
<p class=MsoNormal><span lang=EN-GB style='font-size:11.0pt;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"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b>On Behalf Of </b>Deutsch,
Sarah B<br>
<b>Sent:</b> Tuesday, October 27, 2009 2:43 AM<br>
<b>To:</b> Marilyn Cade; Philip Sheppard; bc - GNSO list<br>
<b>Subject:</b> RE: [bc-gnso] BC charter v19<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I concur that the idea of a one year term should be given serious
consideration. The IPC has followed this model and it works well.</span><span
lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I see that the overly broad "solidarity"
language still remains in the draft. Despite suggestions to try
to figure how how more accurately the language to situations where members are
speaking publicly to the ICANN community, the language remains unchanged.
As Marilyn notes correctly below, instead of drafting solidarity language
that actually explains what the problem is and how to implement it in a
narrow manner, the draft goes in the opposite direction by allowing
executive committee members a carve out from BC positions when they speak in
their personal capacity. If anyone has an obligation to adhere to the
"solidarity" principle without the opportunity to give mixed messages
publicly or privately, it should be executive committee members.</span><span
lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Finally, I note that the troubling privacy language remains in
the draft unchanged. No one has answered the fundamental question of
whether ordinary BC members will be gaining access to personally identifiable
or sensitive personal information (and what information that
is) and how ordinary BC members are allegedly "processing"
such information. Other BC members can weigh in, but we do not want to
have any access to sensitive personal information as part of our BC
membership. As mentioned earlier, requiring compliance with "prevailing
privacy laws" is meaningless since such laws differ signficantly
depending on jurisdiction. At a minimum ONLY the Secretariat and Exec
Committee Members should be subject to this language assuming they may
have access to sensitive personal information. </span><span lang=EN-GB
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Sarah</span><span lang=EN-GB style='font-size:10.0pt;font-family:
"Verdana","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Sarah B. Deutsch<br>
Vice President & Associate General Counsel<br>
Verizon Communications<br>
Phone: 703-351-3044<br>
Fax: 703-351-3670<br>
sarah.b.deutsch@verizon.com</span><span lang=EN-GB style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
<div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p>
</div>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> owner-bc-gnso@icann.org
[mailto:owner-bc-gnso@icann.org] <b>On Behalf Of </b>Marilyn Cade<br>
<b>Sent:</b> Monday, October 26, 2009 1:25 AM<br>
<b>To:</b> Philip Sheppard; bc - GNSO list<br>
<b>Subject:</b> RE: [bc-gnso] BC charter v19</span><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
Philip, thanks.<br>
a few initial comments, and then I'll read through again and flag any areas for
the BC members of concern to me.<br>
<br>
I appreciate that you have now been able to incorporate some of my comments in
this version.<br>
However, I had asked to have a specially designated elected member as the
primary CSG rep, and I'd like that added into the list of elected
positions. There seems clear merit to distributing work, and avoiding
conflicts of interests by putting too many roles into a single party, or small
number of individuals. Spreading work, makes lighter work loads, as we all
know. It does mean that coordination are important, of course. <br>
<br>
A change that I feel strongly about is that the officers should have only one
year terms, with a term limit of no more than three yaers. That is what
the IPC does, and it seems prudent to move to one year terms. <br>
<br>
In 4.8, we need to make the description consistent within the body of the
section to secretariat services, rather than continue to use the term
"Secretariat", since the members haven't supported a continuation of
a retained position, and the approach being proposed will allow flexibility to
either use contracted services or services from ICANN. <br>
<br>
I see that this now proposes that executive committee members need not
adhere to the BC position. This goes too far. If one is an elected officer,
then one has a duty to adhere to the BC position. Can we discuss when you would
envision an executive committee member 'acting in their individual capacity'?
That might clear up the confusion for me on that one. <br>
<br>
I see that this charter is continuing to propose a list administrator. I'm
not sure that is a separate function from 'secretariat services'. We want to
avoid creating someone who is the 'email police', who has to make judgements
about other members communications; I don't see that function in other
constituencies -- and suggest that we simply have principled approaches to
efficient communications.<br>
<br>
We can briefly discuss the CSG representative at the huddle this p.m. <br>
<br>
Marilyn<br>
<br>
<br>
<br>
<br>
> Date: Mon, 26 Oct 2009 05:27:20 +0100<br>
> Subject: [bc-gnso] BC charter v19<br>
> From: philip.sheppard@aim.be<br>
> To: bc-gnso@icann.org<br>
> <br>
> <br>
> I attach the latest version for discussion.<br>
> I believe we are nearly there.<br>
> It factors in the majority of clarifying redrafts that have been suggested<br>
> with the exception of redrafts that replaced current charter text that was<br>
> to date unaltered.<br>
> <br>
> I will pull out those few remaining bigger changes that have been proposed<br>
> for discussion at the BC meeting in Seoul.<br>
> <br>
> Philip<br>
> <o:p></o:p></span></p>
</div>
<br clear=all> This message and its attachments may contain legally privileged or
confidential information. It is intended solely for the named
addressee. If you are not the addressee indicated in this message
(or responsible for delivery of the message to the addressee), you
may not copy or deliver this message or its attachments to anyone.
Rather, you should permanently delete this message and its
attachments and kindly notify the sender by reply e-mail. Any
content of this message and its attachments that does not relate to
the official business of News America Incorporated or its
subsidiaries must be taken not to have been sent or endorsed by any
of them. No representation is made that this email or its
attachments are without defect.
</body>
</html>