<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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 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;}
/* 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";
        color:black;}
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;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;
        color:black;}
span.EmailStyle20
        {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]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks Bene. <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'>So Marilyn, re your Proposal No. 8 again, there was minimal discussion on the call. Bill Smith reiterated general operational concerns with the skeletal concept. Steve referred us back to prior BC support for a GPML concept, involving famous marks only, which died when it became evident that there is no workable way to define fame, among other reasons. Initially you said this is your proposal, then you said that “a number of members support it.” At the moment that number appears to be “one” since nobody else has publicly supported even the bare concept, as far as I can tell from tracking the BC List. Until you answer some of the questions I and others have raised, there simply is no proposal that anyone can reasonably consider, and so the idea should be dropped from further discussion (as a general waste of time) until you do try to answer some of those questions.<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'>Here’s one more too: what if there might be several owners of the same mark? United, Delta, probably a million other marks are registered to different parties in different places for different things. What if one of them wants to register in a new TLD, but another one of them has placed a permanent block? From your perspective, does that seem potentially unfair? How would you propose to address that issue?<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'>Mike<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><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Mike Rodenbaugh<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>RODENBAUGH LAW<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>tel/fax: +1.415.738.8087<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://rodenbaugh.com"><span style='color:blue'>http://rodenbaugh.com</span></a> <o:p></o:p></span></p></div><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'> owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b>On Behalf Of </b>Benedetta Rossi<br><b>Sent:</b> Wednesday, January 11, 2012 8:48 AM<br><b>To:</b> Marilyn Cade<br><b>Cc:</b> bc - GNSO list<br><b>Subject:</b> Re: [bc-gnso] Posting the list of "improvements" to the new gTLD program to the BC public list<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dear Members,<br><br>Please find attached the transcript for yesterday's BC Call. I have also posted it to the BC Wiki in the teleconference section, along with all other transcripts and reports. <br><br>As requested, I have also posted the document regarding the list of improvements to the new gTLD program to the Wiki. <br><br>As a reminder, the BC Wiki can be found here: <a href="https://community.icann.org/display/gnsobc/Home">https://community.icann.org/display/gnsobc/Home</a> <o:p></o:p></p><pre>Kind Regards,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Benedetta Rossi<o:p></o:p></pre><pre>BC Secretariat<o:p></o:p></pre><pre><a href="https://community.icann.org/display/gnsobc/Home">https://community.icann.org/display/gnsobc/Home</a><o:p></o:p></pre><pre><a href="http://www.bizconst.org">www.bizconst.org</a><o:p></o:p></pre><pre><a href="mailto:bc-secretariat@icann.org">bc-secretariat@icann.org</a><o:p></o:p></pre><p class=MsoNormal><br>On 11/01/2012 00:12, Marilyn Cade wrote: <o:p></o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>Two members asked to have this list posted to the bc-GNSO list. Thus, I am posting it, but you already received it via bc-private, so you can disregard this. It is a copy of the list provided for the BC call. <br> <br>Bene will also put it on the BC WIKI, and as she and I finalize the grid/excel version, we will get that posted to members. As noted in the earlier email, I am targeting providing it to the ExComm for a sanity check on readability and undertandabiilty for members comments on the document, and then posting to the bc-GNSO list. <br> <br>Just a reminder that you will have the transcript from Bene, our Secretariat in a few days, or sooner, as well, as a memory supplement, or if someone in your company missed the call and you want to engage with them on the discussions. <br> <br>Marilyn Cade<o:p></o:p></p></div></div></body></html>