<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
et me first respond to Sarah's suggestion about some of what was in the marked up version of the Current BC Charter. I'll look at what Sarah did, and then comment on top of her comments on what is being called v.16. That won't happen until early Thursday, since I'm crashing on work related to broader ICANN comments re the meta issues of accountability, etc. <div style="text-indent: 0in !important; "><br style="text-indent: 0in !important; "></div><div style="text-indent: 0in !important; ">That way, Sarah's comments, my comments will all be in 'version v.16'. </div><div style="text-indent: 0in !important; "><br style="text-indent: 0in !important; "></div><div style="text-indent: 0in !important; ">I think we have to try to have coherent and thoughtful discussions about some of these issues and they can't take place on the fly, or under a crisis time frame, or without the full ability of a broad and diverse group of members to participate. Perhaps all of us can come away from the Seoul meeting with a better and broader understanding about schedules with a better understanding of how the GNSO restructuring is progressing, and what flexibility there is. </div><div style="text-indent: 0in !important; "><br></div><div style="text-indent: 0in !important; "><br></div><div style="text-indent: 0in !important; "><br></div><br><br><br><hr id="stopSpelling">Subject: [bc-gnso] Clarification as to which draft Charter to comment upon<br>Date: Wed, 21 Oct 2009 10:52:24 -0600<br>From: RAnderson@interborder.ca<br>To: bc-gnso@icann.org<br><br>
<style>
.ExternalClass p.ecx37073324-da35-4b1e-9b54-d72bbcf6b888, .ExternalClass li.ecx37073324-da35-4b1e-9b54-d72bbcf6b888, .ExternalClass div.ecx37073324-da35-4b1e-9b54-d72bbcf6b888, .ExternalClass table.ecx37073324-da35-4b1e-9b54-d72bbcf6b888Table
{margin-bottom:.0001pt;}
.ExternalClass div.ecxSection1
{page:Section1;}
</style>
<style>
.ExternalClass .ecxshape
{;}
</style>
<style>
@page Section1
{size:612.0pt 792.0pt;}
.ExternalClass P.ecxMSONORMAL
{;}
.ExternalClass LI.ecxMSONORMAL
{;}
.ExternalClass DIV.ecxMSONORMAL
{;}
.ExternalClass A:link
{;}
.ExternalClass SPAN.ecxMSOHYPERLINK
{;}
.ExternalClass A:visited
{;}
.ExternalClass SPAN.ecxMSOHYPERLINKFOLLOWED
{;}
.ExternalClass SPAN.ecxEMAILSTYLE17
{;}
.ExternalClass .ecxMSOCHPDEFAULT
{;}
.ExternalClass TABLE.ecxMSONORMALTABLE
{;}
.ExternalClass P.ecxMsoNormal
{font-size:11pt;font-family:'Times New Roman';}
.ExternalClass LI.ecxMsoNormal
{font-size:11pt;font-family:'Times New Roman';}
.ExternalClass DIV.ecxMsoNormal
{font-size:11pt;font-family:'Times New Roman';}
.ExternalClass A:link
{color:blue;text-decoration:underline;}
.ExternalClass SPAN.ecxMsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass A:visited
{color:purple;text-decoration:underline;}
.ExternalClass SPAN.ecxMsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
.ExternalClass SPAN.ecxEmailStyle17
{color:windowtext;font-family:'Times New Roman';}
.ExternalClass SPAN.ecxEmailStyle18
{color:navy;font-family:Arial;}
.ExternalClass DIV.ecxSection1
{page:Section1;}
</style>
<p class="ecx37073324-da35-4b1e-9b54-d72bbcf6b888"><span lang="EN-US" style="font-family:'Times New Roman','serif'"><span lang="EN-US" style="font-family:'Times New Roman','serif'"><font size="2"></font></span></span></p><font size="2"><font color="navy" face="Arial" size="2">
I am concerned about the point regarding the same companies and even individuals participating in multiple constutuencies <br><br>("On a related topic, we think it is important to delete the section on "divisional separation" as many BC members, large and small, have limited resources and should have the flexibility to have the same person or overlapping persons representing them on different constituencies.")<br><br>In my view we are going ever deeper down the wrong path here. The premise of ICANN's multiple constituency structure is to afford different voices a method to be heard, and to share knowledge, expertise and perspective with like-minded peers along with participating in the broader community. But the morphing of this into the idea that the same organization or even person can wear mutliple hats and participate as a registrar or registry one day and a user the next, this seems wrong to me and at odds with the premise.<br><br>Can we not find of way of permitting people to sit in and contribute up to a point in various constituencies - in the interests of cross-fertilization and acknowledging that the same organization can have different activities - while at the same time requiring each member organization to declare one or another area as their principle interest vis-a-vis ICANN and that that constituency is the place where they have full membership and voting etc?<br><br>Thus will get somewhat easier if/when we ever actually get on with creating the commercial group, but in the meantime, let's not more deeply embed a bad practice.<br><br>cheers/Rick<br><br>Rick Anderson<br>EVP, InterBorder Holdings Ltd<br>email: randerson@interborder.ca<br>cell: (403) 830-1798<br></font><BR>
<BR><hr align="center" size="2" width="100%">
<font face="Tahoma" size="2">
<b>From</b>: owner-bc-gnso@icann.org <br><b>To</b>: HASSAN Ayesha ; BC Secretariat ; BC gnso <br><b>Sent</b>: Wed Oct 21 10:00:55 2009<br><b>Subject</b>: RE: [bc-gnso] Clarification as to which draft Charter to comment upon<br></font><BR>
<div align="left" dir="ltr"><span class="ecx432373215-21102009"><font color="#0000ff" face="Arial" size="2">All,</font></span></div><span class="ecx432373215-21102009"><font color="#0000ff" face="Arial" size="2"></font>
<div align="left" dir="ltr"><br><font face="Arial"><font color="#0000ff"><font size="2">I
would like to suggest some initial changes to version 16 of the draft charter,
which includes the <span class="ecx432373215-21102009">good </span>change Ayesha
inserted below. <span class="ecx432373215-21102009">On a related
topic</span>, <span class="ecx432373215-21102009">we think </span><span class="ecx432373215-21102009">it is important to delete the section on
"</span>divisional separation<span class="ecx432373215-21102009">" as
</span>many <span class="ecx432373215-21102009">BC members, large and
small,</span> have limited resources and shou<span class="ecx432373215-21102009">ld have the flexibility </span>to have the same person
or overlapping persons representing them on different constituenc<span class="ecx432373215-21102009">ies</span>. </font></font></font></div>
<div align="left" dir="ltr"><font face="Arial"><font color="#0000ff"><font size="2"></font></font></font> </div>
<div align="left" dir="ltr"><font face="Arial"><font color="#0000ff"><font size="2"><span class="ecx432373215-21102009">You'll see a number of other edits, including those
that soften the </span>tone of the charter<span class="ecx432373215-21102009">,</span><span class="ecx432373215-21102009">
</span>focus<span class="ecx432373215-21102009">ing</span> more on <span class="ecx432373215-21102009">reasonable practices </span>and less on<span class="ecx432373215-21102009"> sanctions. </span></font></font></font><font face="Arial"><font color="#0000ff"><font size="2"><span class="ecx432373215-21102009">For
example, although I understand the intent behind the "solidarity clause," the
language about "remaining faithful to approved positions" is too vague and
sounds somewhat totalitarian. Both companies and individuals' positions can
change. I don't think we need this language in light of the other language
in the charter on expected standards of
behavior. </span></font></font></font></div>
<div align="left" dir="ltr"><font face="Arial"><font color="#0000ff"><font size="2"><span class="ecx432373215-21102009"></span></font></font></font> </div>
<div align="left" dir="ltr"><font face="Arial"><font color="#0000ff"><font size="2"><span class="ecx432373215-21102009">I also made changes to clarify that the
Consitutency as a whole should decide which issues are priority policy
issues. The role of the vice chair for policy should more
reasonably be to coordinate with members as to which policies are
priorities, not to make those decisions unilaterally. Finally, I
deleted the provision about compliance with "prevailing privacy laws" since
there are literally thousands of laws and regulations around the world
and no one BC member can reasonably be expected to know them all. The
language requiring general compliance with the care of personal data should
be sufficient.</span></font></font></font></div>
<div align="left" dir="ltr"><font color="#0000ff" face="Arial" size="2"><span class="ecx432373215-21102009"></span></font> </div>
<div align="left" dir="ltr"><font color="#0000ff" face="Arial" size="2"><span class="ecx432373215-21102009"></span></font><span class="ecx432373215-21102009"><font color="#0000ff" face="Arial" size="2">Note that all of
these are initial proposed changes to this document only. I also liked the
draft charter that Marilyn posted earlier and saw it as largely
non-controversial. If it is not feasible to work off the many good
suggestions in her draft, Marilyn should be provided with the opportunity
to insert the best aspects of that document into the current draft for further
consideration. </font></span></div>
<div align="left" dir="ltr"><span class="ecx432373215-21102009"><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div align="left" dir="ltr"><span class="ecx432373215-21102009"><font color="#0000ff" face="Arial" size="2">Sarah</font></span></div>
<div><font color="#0000ff" face="Arial" size="2"></font> </div>
<div align="left"><br><font size="2"><font color="#000080"><font face="Arial">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</font></font></font></div>
<div> </div><br>
<div align="left" class="ecxOutlookMessageHeader" dir="ltr" lang="en-us">
<hr>
<font face="Tahoma" size="2"><b>From:</b> owner-bc-gnso@icann.org
[mailto:owner-bc-gnso@icann.org] <b>On Behalf Of </b>HASSAN
Ayesha<br><b>Sent:</b> Wednesday, October 21, 2009 6:14 AM<br><b>To:</b> BC
Secretariat; BC gnso<br><b>Subject:</b> RE: [bc-gnso] Clarification as to which
draft Charter to comment upon<br></font><br></div>
<div></div>
<div class="ecxSection1">
<p class="ecxMsoNormal"><b><font face="Times New Roman" size="2"><span style="font-weight:bold;font-size:11pt">Dear
colleagues,</span></font></b></p>
<p class="ecxMsoNormal"><b><font face="Times New Roman" size="2"><span style="font-weight:bold;font-size:11pt"> </span></font></b></p>
<p class="ecxMsoNormal"><b><font face="Times New Roman" size="2"><span style="font-weight:bold;font-size:11pt">I would like to suggest the addition
of clear language in 3.3.2 to ensure that business associations like ICC and
others who have members who belong to other ICANN constituencies are not
excluded from BC membership because of the range of their membership. See
suggested addition below in yellow highlighting and underlined. Text to this
effect would ensure that business organizations like ICC, USCIB and others can
remain BC members.</span></font></b></p>
<p class="ecxMsoNormal"><b><font face="Times New Roman" size="2"><span style="font-weight:bold;font-size:11pt">Best
regards,</span></font></b></p>
<p class="ecxMsoNormal"><b><font face="Times New Roman" size="2"><span style="font-weight:bold;font-size:11pt">Ayesha</span></font></b></p>
<p class="ecxMsoNormal"><b><font face="Times New Roman" size="2"><span style="font-weight:bold;font-size:11pt"> </span></font></b></p>
<p class="ecxMsoNormal"><b><font face="Times New Roman" size="2"><span style="font-weight:bold;font-size:11pt">3.3.</span></font></b> <b><span style="font-weight:bold">Membership Criteria</span></b></p>
<p class="ecxMsoNormal"><font face="Times New Roman" size="2"><span style="font-size:11pt">3.3.1 In keeping with the selective membership criteria
of other GNSO constituencies, the Business Constituency represents the interests
of a specific sector of Internet users. The purpose of the Constituency is to
represent the interests of businesses described in Article
3.1.</span></font></p>
<p class="ecxMsoNormal"><font face="Times New Roman" size="2"><span style="font-size:11pt"> </span></font></p>
<p class="ecxMsoNormal"><font face="Times New Roman" size="2"><span style="font-size:11pt">3.3.2 To avoid conflicts of interest this excludes: not
for profit entities excepting trade associations representing for profit
entities; entities whose prime business is a registry, registry operator,
prospective registry, registrar, reseller, other domain name supplier interests,
or similar; other groups whose interests may not be aligned with business users
described in Article 3.1. <u><span style="background:yellow">Trade associations
whose members may also include companies/associations that belong to or could
belong to any of the other ICANN constituencies are not excluded from BC
membership.</span></u></span></font></p>
<p class="ecxMsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size:10pt;color:navy;font-family:Arial"> </span></font></p>
<p class="ecxMsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size:10pt;color:navy;font-family:Arial"> </span></font></p>
<div>
<div align="center" class="ecxMsoNormal" style="text-align:center"><font face="Times New Roman" size="3"><span style="font-size:12pt">
<hr align="center" size="2" width="100%">
</span></font></div>
<p class="ecxMsoNormal"><b><font face="Tahoma" size="2"><span style="font-weight:bold;font-size:10pt;font-family:Tahoma">From:</span></font></b><font face="Tahoma" size="2"><span style="font-size:10pt;font-family:Tahoma">
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b><span style="font-weight:bold">On Behalf Of </span></b>BC Secretariat<br><b><span style="font-weight:bold">Sent:</span></b> mercredi 21 octobre 2009
11:19<br><b><span style="font-weight:bold">To:</span></b> BC gnso<br><b><span style="font-weight:bold">Subject:</span></b> [bc-gnso] Clarification as to
which draft Charter to comment upon</span></font><font size="3"><span style="font-size:12pt"></span></font></p></div>
<p class="ecxMsoNormal"><font face="Times New Roman" size="2"><span style="font-size:11pt"> </span></font></p>
<div>
<p class="ecxMsoNormal"><font face="Arial" size="2"><span lang="EN-GB" style="font-size:10pt;font-family:Arial">Posted on behalf of the BC
Officers</span></font><font size="3"><span lang="EN-GB" style="font-size:12pt"></span></font></p></div>
<p class="ecxMsoNormal"><font face="Times New Roman" size="2"><span lang="EN-GB" style="font-size:11pt"> </span></font></p>
<p class="ecxMsoNormal"><font face="Times New Roman" size="2"><span lang="EN-GB" style="font-size:11pt"> </span></font></p>
<p class="ecxMsoNormal"><font face="Times New Roman" size="2"><span lang="EN-GB" style="font-size:11pt">Dear Members,</span></font></p>
<p class="ecxMsoNormal"><font face="Times New Roman" size="2"><span lang="EN-GB" style="font-size:11pt"> </span></font></p>
<p class="ecxMsoNormal"><font face="Times New Roman" size="2"><span lang="EN-GB" style="font-size:11pt">Consequent to some queries regarding which draft of the
Charter members should comment upon. For clarification and to save the
little time left in terms of the Charter submission please note that the Charter
under discussion and for comments is the ‘BC charter 2009 v16.doc’ which is
attached for members’ convenience.</span></font></p>
<p class="ecxMsoNormal"><font face="Times New Roman" size="2"><span lang="EN-GB" style="font-size:11pt"> </span></font></p>
<p class="ecxMsoNormal"><font face="Times New Roman" size="2"><span lang="EN-GB" style="font-size:11pt">BC Officers</span></font></p>
<p class="ecxMsoNormal"><font color="#1f497d" face="Times New Roman" size="2"><span style="font-size:10pt;color:#1f497d"> </span></font></p>
<p class="ecxMsoNormal"><font color="#1f497d" face="Times New Roman" size="2"><span style="font-size:10pt;color:#1f497d"> </span></font></p></div></span></font><BR>
<p class="ecx37073324-da35-4b1e-9b54-d72bbcf6b888"><span lang="EN-US" style="font-family:'Times New Roman','serif'"><span lang="EN-US" style="font-family:'Times New Roman','serif'"><font size="2"></font></span></span> </p>
<p class="ecx37073324-da35-4b1e-9b54-d72bbcf6b888"><span lang="EN-US" style="font-family:'Times New Roman','serif'"><span lang="EN-US" style="font-family:'Times New Roman','serif'"><font size="2"></font></span></span> </p>
<p class="ecx37073324-da35-4b1e-9b54-d72bbcf6b888"><span lang="EN-US" style="font-family:'Times New Roman','serif'"><span lang="EN-US" style="font-family:'Times New Roman','serif'"><font size="2">This e-mail message and any attachments may contain confidential and/or privileged information intended only for the addressee. In the event this e-mail is sent to you in error, sender and sender’s company do not waive confidentiality or privilege, and waiver may not be assumed.<span style=""> </span>Any dissemination, distribution or copying of, or action taken in reliance on, the contents of this e-mail by anyone other than the intended recipient is prohibited.<span style=""> </span>If you have been sent this e-mail in error, please destroy all copies and notify sender at the above e-mail address.</font></span></span></p>
<p class="ecxMsoNormal" style=""><span lang="EN-US" style="font-family:'Times New Roman','serif'"><font size="2"> </font></span></p>
<p class="ecxMsoNormal" style=""><font size="2"><span lang="EN-US" style="font-family:'Times New Roman','serif'">Computer viruses can be transmitted by e-mail.<span style=""> </span>You should check this e-mail message and any attachments for viruses.<span style=""> </span>Sender and sender’s company accept no liability for any damage caused by any virus transmitted by this e-mail.<span style=""> </span>Like other forms of communication, e-mail communications may be vulnerable to interception by unauthorized parties.<span style=""> </span>If you do not wish to communicate by e-mail, please notify sender.<span style=""> </span>In the absence of such notification, your consent is assumed.<span style=""> </span>Sender will not take any additional security measures (such as encryption) unless specifically requested.</span><span style="color:blue;font-family:'Arial','sans-serif'"></span></font></p><span></span>                                            </body>
</html>