<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [gnso-dow123] FW: MarkMonitor's WHOIS Comments
- To: ross@xxxxxxxxxx
- Subject: Re: [gnso-dow123] FW: MarkMonitor's WHOIS Comments
- From: maggie.mansourkia@xxxxxxxxxxx
- Date: Tue, 23 Jan 2007 18:03:38 -0500
<br><font size=2 face="sans-serif">Demonstrable to who?? to whom??
Pardon the grammar, but you get the point. What Verizon supports
is that organizations indicate their respective positions via the process
established by ICANN, rather than through private conversations with a
task force member. </font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Ross Rader"
<ross@xxxxxxxxxx></b> </font>
<p><font size=1 face="sans-serif">01/23/2007 05:52 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
ross@xxxxxxxxxx</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">Magnolia
Mansourkia/EMPL/VA/Verizon@VZNotes</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top><font size=1 face="sans-serif">gnso-dow123@xxxxxxxxxxxxxx,
"Metalitz, Steven" <met@xxxxxxx>,
owner-gnso-dow123@xxxxxxxxx</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Re: [gnso-dow123] FW:
MarkMonitor's
WHOIS Comments</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>So even though there are demonstrable issues with
a portion of the <br>
dataset, you would like us to proceed on faith that the rest of the <br>
dataset is valid? That makes no sense whatsoever.<br>
<br>
As far as the audit activities go, there were several organizations <br>
listed on their submission that have taken very strong pro-privacy and
<br>
pro-internet positions in the past. Positions that were completely <br>
contrary to what MarkMonitor was espousing. It didn't take much in terms
<br>
of executive level investigation to find substantial issues with <br>
MarkMonitor's representations about the status of the
"co-signators".<br>
<br>
This document should be viewed as one document espousing one set of <br>
views and not be given any special consideration because of the weight
<br>
of the supposed support that comes with it.<br>
<br>
Following through with your logic, I will start opting companies into my
<br>
positions without their knowledge, but give them the opportunity to <br>
write ICANN and let the TF know that they don't really support my <br>
position. Verizon supports this approach, as does the MPAA and AT&T.
And <br>
if they don't, have them write in to let us know that I've mispresented
<br>
your views.<br>
<br>
maggie.mansourkia@xxxxxxxxxxx wrote:<br>
> Ok, I didn't realize that we'd been tasked with "auditing"
submissions and I'm <br>
> getting confused. The companies listed are not single person
organization, and <br>
> if someone with authority to do so, signed onto a letter, and yet
someone else <br>
> at the company is not aware of it, why would we have authority (or
even the <br>
> time) to second guess the organization's position?<br>
> <br>
> It seems to me that if a company was inappropriately listed, then
it is <br>
> incumbent upon the organization to submit a statement to ICANN in
that regard, <br>
> regardless of whether they wish to advocate any position at all.
Since
most of <br>
> the names listed are substantial companies with household names and
very strong <br>
> representation, it doesn't seem likely that they were somehow fooled
by <br>
> MarkMonitor to endorse a position if they do not in fact do so. <br>
> <br>
> If any of the organizations indicate that the organization's name
does not <br>
> belong on the letter, then it should certainly be noted along with
other <br>
> submissions, but I'm not sure how a private conversation with one
member of a <br>
> task force is supposed to be indicative of several organizations'
positions. <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> *"Ross Rader" <ross@xxxxxxxxxx>*<br>
> Sent by: owner-gnso-dow123@xxxxxxxxx<br>
> <br>
> 01/23/2007 01:26 PM<br>
> Please respond to<br>
> ross@xxxxxxxxxx<br>
> <br>
> <br>
> <br>
> To<br>
>
"Metalitz,
Steven" <met@xxxxxxx><br>
> cc<br>
>
gnso-dow123@xxxxxxxxxxxxxx<br>
> Subject<br>
> Re:
[gnso-dow123] FW: MarkMonitor's WHOIS Comments<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> Despite this, the interactions I have had with those who supposedly<br>
> support this document, have in fact turned out not to support this<br>
> document. I have not contacted over 100 companies, nor will I, but
in<br>
> the small audit that I conducted, a clear majority of those listed
as<br>
> signatories, were in fact ignorant of the issues and not supportive
of<br>
> the MarkMonitor position.<br>
> <br>
> I think its fine to accept the MarkMonitor submission at face value,
but<br>
> I would also like to ensure that the official record is clear that
those<br>
> listed as signatories are not necessarily supportive of the positions<br>
> espoused and the number of signatures should not be given any weight
in<br>
> our, or ensuing, deliberations.<br>
> <br>
> -ross<br>
> <br>
> Metalitz, Steven wrote:<br>
> > fyi, in response to Ross's post yesterday<br>
> ><br>
> > ________________________________<br>
> ><br>
> > From: Margie Milam [mailto:Margie.Milam@xxxxxxxxxxxxxxx]<br>
> > Sent: Tuesday, January 23, 2007 1:00 PM<br>
> > To: Metalitz, Steven<br>
> > Subject: MarkMonitor's WHOIS Comments<br>
> ><br>
> ><br>
> ><br>
> > Steve,<br>
> ><br>
> > <br>
> ><br>
> > I understand that a question has been raised regarding
the MarkMonitor<br>
> > Comments to the WHOIS Taskforce Report. <br>
> ><br>
> > <br>
> ><br>
> > The MarkMonitor letter represents the collective perspective
of over 100<br>
> > companies, non-profit groups and other organizations concerned
about the<br>
> > impact of WHOIS policy on their ability to protect their
customers. We<br>
> > stand by these endorsements and wish to provide the WHOIS
Task Force<br>
> > additional information regarding the process by which these
endorsements<br>
> > were collected. <br>
> ><br>
> > <br>
> ><br>
> > We obtained the endorsements through an email communication
that was<br>
> > sent primarily to our clients and to other organizations
interested in<br>
> > the WHOIS issue. The email contained a link to a
website page<br>
> > describing MarkMonitor's Comments, and requested that the
endorser enter<br>
> > their name, email address and Company if they supported
the statements<br>
> > on behalf of their organization. <br>
> ><br>
> > <br>
> ><br>
> > Those who responded were sent a confirming email (to the
email address<br>
> > they provided) with the following message:<br>
> ><br>
> > <br>
> ><br>
> > "Thank you for your rapid response in support
of this important issue.<br>
> > We will include your company name in the letter we plan
on submitting to<br>
> > ICANN early next week in favor of the Special Circumstances
Proposal.<br>
> ><br>
> > <br>
> ><br>
> > We are also publishing that letter on our web site at:<br>
> > http://www.markmonitor.com/openwhois/ in order to call
attention to this<br>
> > important issue. Please feel free to contact me at
415-278-8472<br>
> > (honni.marks@xxxxxxxxxxxxxxx) or Margie Milam at
208-389-5750<br>
> > (margie.milam@xxxxxxxxxxxxxxx) if you have any additional
questions or<br>
> > concerns. Again, we appreciate your support and thank you
for response."<br>
> ><br>
> > <br>
> ><br>
> > We know that many of the endorsements resulted from consultation
and<br>
> > coordination within the endorsing entities. For
example, in the case<br>
> > of the Anti-Phishing Working Group, this endorsement was
made after a<br>
> > vote by its steering committee to endorse the MarkMonitor
position. <br>
> ><br>
> > <br>
> ><br>
> > There were also a few endorsements that resulted after
an article<br>
> > appeared in eweek.com regarding this issue (see<br>
> > http://www.eweek.com/article2/0,1895,2082346,00.asp<br>
> > <http://www.eweek.com/article2/0,1895,2082346,00.asp>
), which<br>
> > resulted in our updated posting on 1/15/07. These
endorsements were<br>
> > confirmed in the same manner as the email communications
described<br>
> > above.<br>
> ><br>
> > <br>
> ><br>
> > We are not aware of any concerns regarding the information
provided,<br>
> > except for a Mozilla reference which was corrected last
week to be an<br>
> > "individual" endorsement instead of a
"corporate"
endorsement. In<br>
> > addition, yesterday we were informed that dot.berlin has
reconsidered<br>
> > its prior endorsement. <br>
> ><br>
> > <br>
> ><br>
> > As you know, over the past few years ICANN has sought a
broader scope of<br>
> > participation on major issues, including WHOIS issues.
The participation<br>
> > by major corporations and non-profit organizations in this
discussion<br>
> > through their endorsement of the MarkMonitor letter is
in line with<br>
> > ICANN's efforts to seek greater participation, and should
therefore be<br>
> > considered in the Task Force's analysis.
<br>
> ><br>
> > <br>
> ><br>
> > If you have any further questions regarding our posting,
please do not<br>
> > hesitate to contact me at (208) 389-5769.<br>
> ><br>
> > <br>
> ><br>
> > Sincerely,<br>
> ><br>
> > <br>
> ><br>
> > Margie Milam<br>
> ><br>
> > General Counsel<br>
> ><br>
> > MarkMonitor, Inc.<br>
> ><br>
> > <br>
> ><br>
> ><br>
> <br>
> <br>
> <br>
<br>
<br>
</tt></font>
<br>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|