<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>Responding to request from Marilyn, in preparation for tomorrow's BC call.</div>
<div><br>
</div>
<div>Attached is a matrix showing GAC's Beijing Advice, BC positions, and what ICANN's Board has said so far.</div>
<div><br>
</div>
<div>For reference:</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>The GAC Beijing Advice is <a href="http://www.icann.org/en/news/correspondence/gac-to-board-18apr13-en.pdf ">
here</a>.</div>
<div>BC Comments on GAC Safeguards is <a href="http://www.bizconst.org/Positions-Statements/BC%20Comment%20on%20GAC%20Advice%20for%20new%20gTLDs%20FINAL[4].pdf ">
here</a>. </div>
<div>Board New gTLD Program Committee's 4-Jun resolution is <a href="http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-04jun13-en.htm">
here</a>.</div>
<div>
<div><span class="Apple-style-span">Board New gTLD Program Committee's 25-Jun resolution is
<a href="http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-25jun13-en.htm">
here</a>.</span></div>
</div>
</blockquote>
<div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div><br>
</div>
</blockquote>
<div>-- </div>
<div>Steve</div>
<div><br>
</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Optima; font-size:10pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Marilyn Cade <<a href="mailto:marilynscade@hotmail.com">marilynscade@hotmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Sunday, June 30, 2013 1:30 AM<br>
<span style="font-weight:bold">To: </span>Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>>, bc - GNSO list <<a href="mailto:bc-gnso@icann.org">bc-gnso@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>RE: [bc-gnso] Latest ICANN New gTLD Committee resolutions on GAC Advice from Beijing<br>
</div>
<div><br>
</div>
<div><style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div class="hmmessage">
<div dir="ltr">Thanks, Steve.
<div><br>
</div>
<div>Perhaps we want to sort of do a check list of our own, on what the Board accepted from GAC advice, that was consistent, or partly consistent with our own strong and ongoing input to the Board, public forums, public comments, and GAC.
<div><br>
</div>
<div>
<div>
<div>
<div>
<hr id="stopSpelling">
From: <a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a><br>
To: <a href="mailto:bc-gnso@icann.org">bc-gnso@icann.org</a><br>
Subject: [bc-gnso] Latest ICANN New gTLD Committee resolutions on GAC Advice from Beijing<br>
Date: Sun, 30 Jun 2013 01:08:33 +0000<br>
<br>
<div>
<div>
<div>ICANN's New gTLD Program Committee (NGPC) agreed to several aspects of GAC advice. (<a href="http://www.icann.org/en/news/announcements/announcement-27jun13-en.htm" target="_blank">link</a>)</div>
</div>
</div>
<div><br>
</div>
<span id="ecxOLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap:break-word;color:rgb(0, 0, 0);font-size:16px;font-family:Calibri, sans-serif;">
<div>Overall, the NGPC concluded that acceptance and implementation of GAC safeguards would bring less delay and uncertainty than the protracted consultations required if ICANN rejects GAC advice.</div>
</div>
</div>
</span>
<div>
<div>
<div>
<div><br>
</div>
<div>Safeguards for all gTLDs</div>
<blockquote style="border-top-style:none;border-right-style:none;border-bottom-style:none;border-left-style:none;border-width:initial;border-color:initial;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px;">
<div>Governments should appreciate that ICANN takes ownership of WHOIS accuracy checks. </div>
<div><br>
</div>
<div>GAC advised ICANN to "ensure there are real and immediate consequences" for safeguard violations. ICANN's response is say these violations would "be a basis for suspension". But that's not the same as actually
<u>requiring</u> Registrars to suspend the name if violations are found.</div>
<div><br>
</div>
</blockquote>
</div>
</div>
<div>Restricted gTLDs and exclusive generic TLDs</div>
<blockquote style="border-top-style:none;border-right-style:none;border-bottom-style:none;border-left-style:none;border-width:initial;border-color:initial;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px;">
<div>ICANN accepted safeguards on how TLDs should enforce registrant restrictions that are useful to protect consumers and users. </div>
<div><br>
</div>
<div>That's different from the issue of generic TLDs for the <i>exclusive</i> use of a single company, where ICANN just called a time-out to have further dialogue with the GAC.</div>
<div><br>
</div>
</blockquote>
</div>
<span id="ecxOLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap:break-word;color:rgb(0, 0, 0);font-size:16px;font-family:Calibri, sans-serif;">
<span id="ecxOLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap:break-word;color:rgb(0, 0, 0);font-size:16px;font-family:Calibri, sans-serif;">
<span id="ecxOLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap:break-word;color:rgb(0, 0, 0);font-size:16px;font-family:Calibri, sans-serif;">
<div>
<div>
<div>ICANN will not re-do contention sets between singular and plural versions of the same TLD. </div>
</div>
</div>
</div>
</div>
</span></div>
</div>
</span></div>
</div>
</span>
<div><span id="ecxOLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap:break-word;color:rgb(0, 0, 0);font-size:16px;font-family:Calibri, sans-serif;">
<span id="ecxOLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap:break-word;color:rgb(0, 0, 0);font-size:16px;font-family:Calibri, sans-serif;">
<span id="ecxOLK_SRC_BODY_SECTION">
<div>
<div style="color:rgb(0, 0, 0);font-size:16px;font-family:Calibri, sans-serif;word-wrap:break-word;">
<blockquote style="border-top-style:none;border-right-style:none;border-bottom-style:none;border-left-style:none;border-width:initial;border-color:initial;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px;">
<div>The NGPC did "reconsider" the decision to delegate both singular and plurals, but I doubt the GAC views that as "accepting" their advice. I don't think this issue is closed since nearly everyone sees probable user confusion between the singular and plural
of the exact same TLD. Moreover, this is an awful precedent for the next round, since it would seem to permit new applications for the plural version of existing TLDs, like org(s), net(s), and com(s). </div>
</blockquote>
</div>
</div>
</span></div>
</div>
</span></div>
</div>
</span>
<div><br>
</div>
</div>
<span id="ecxOLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap:break-word;color:rgb(0, 0, 0);font-size:16px;font-family:Calibri, sans-serif;">
<div>
<div>
<div>-- </div>
<div>Steve DelBianco</div>
<div>Executive Director</div>
<div>NetChoice</div>
<div><a href="http://www.NetChoice.org" target="_blank">http://www.NetChoice.org</a> and
<a href="http://blog.netchoice.org" target="_blank">http://blog.netchoice.org</a></div>
<div>+1.202.420.7482 </div>
<div><br>
</div>
</div>
</div>
<span id="ecxOLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap:break-word;color:rgb(0, 0, 0);font-size:16px;font-family:Calibri, sans-serif;">
<span id="ecxOLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap:break-word;color:rgb(0, 0, 0);font-size:16px;font-family:Calibri, sans-serif;">
<span id="ecxOLK_SRC_BODY_SECTION">
<div>
<div style="color:rgb(0, 0, 0);font-size:16px;font-family:Calibri, sans-serif;word-wrap:break-word;">
<blockquote style="border:none;padding:0px;">
<div><br>
</div>
</blockquote>
</div>
</div>
</span></div>
</div>
</span></div>
</div>
</span></div>
</div>
</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>