<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=utf-8"><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:"Avenir Next";
        panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.apple-tab-span
        {mso-style-name:apple-tab-span;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle21
        {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:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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 lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>+1 Steve. And will still be the reason d’etre of a gTLD Round 2 @ 2017. Nothing should be discarded.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Phil<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'><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 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org] <b>On Behalf Of </b>Steve DelBianco<br><b>Sent:</b> 09 January 2016 16:10<br><b>To:</b> Burr, Becky; Accountability Community<br><b>Subject:</b> Re: [CCWG-ACCT] "Consumer Trust" in the Mission Statement<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>Our recommendation #9 is Incorporating the Affirmation of Commitments in ICANN’s Bylaws. That includes commitments made by ICANN in the AoC, such as the commitment cited by Becky, to "promote competition, consumer trust, and consumer choice in the DNS marketplace."<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>First, I don’t think we should casually discard any of those three commitment items just because it is difficult to define. The AoC review that’s just begun will develop working definitions as part of its review.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>I would answer 'No' to both of Becky’s questions. This commitment does not need to be part of Core Values, and could live in the bylaws section describing the required AoC review of any expansion of new gTLDs. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>Since it is in the bylaws, ICANN’s fulfillment of this commitment could be the subject of an IRP. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>And any changes to this commitment would be subject to veto by the empowered community.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-family:"Calibri","sans-serif";color:black'>From: </span></b><span style='font-family:"Calibri","sans-serif";color:black'><<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>> on behalf of Becky Burr <<a href="mailto:Becky.Burr@neustar.biz">Becky.Burr@neustar.biz</a>><br><b>Date: </b>Friday, January 8, 2016 at 2:10 PM<br><b>To: </b>Accountability Community <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><br><b>Subject: </b>[CCWG-ACCT] "Consumer Trust" in the Mission Statement<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><div><div><div><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt'><span style='font-family:"Calibri","sans-serif";color:black'> </span><span style='font-family:"Avenir Next","serif";color:black'> As discussed in our call yesterday, we would like to get some discussion started on some of the issues with the Mission Statement, Commitments & Core Values elements of the CCWG Proposal. One of those issues relates to the inclusion of the concept of promoting “consumer trust” in the Commitments and/or Core Values. The USCIB comment, for example, urged inclusion of a Commitment/Core Value of “promoting competition, consumer trust, and consumer choice in the DNS marketplace.” ALAC urged inclusion of the consumer trust language.</span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt'><span style='font-family:"Avenir Next","serif";color:black'>This is the topic we will discuss on Monday, during the Ad Hoc meeting just announced. Feel free to contribute your views in this thread, particularly if you are not going to be able to participate on Monday.</span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt'><span style='font-family:"Avenir Next","serif";color:black'> <b> ISSUE</b>: Paragraph 3 of the Affirmation of Commitments describes the goals of the AoC, saying: </span><span style='font-family:"Avenir Next","serif";color:#333333;background:white'> </span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><blockquote style='margin-left:30.0pt;margin-right:0cm'><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt'><span style='font-family:"Avenir Next","serif";color:#333333;background:white'> "<i>This document affirms key commitments by </i></span><i><span style='font-family:"Avenir Next","serif";color:black'>DOC</span></i><i><span style='font-family:"Avenir Next","serif";color:#333333;background:white'> and </span></i><i><span style='font-family:"Avenir Next","serif";color:black'>ICANN</span></i><i><span style='font-family:"Avenir Next","serif";color:#333333;background:white'>, including commitments to: … (c) promote competition, consumer trust, and consumer choice in the </span></i><i><span style='font-family:"Avenir Next","serif";color:black'>DNS</span></i><i><span style='font-family:"Avenir Next","serif";color:#333333;background:white'> marketplace….</span></i><i><span style='font-family:"Avenir Next","serif";color:#333333'>”</span></i><i><span style='font-family:"Avenir Next","serif";color:black'> </span></i><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt'><span style='font-family:"Avenir Next","serif";color:black'>Paragraph 9.3 of the AoC says:</span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt'><span style='font-family:"Avenir Next","serif";color:#333333;background:white'> … If and when new gTLDs (whether in ASCII or other language character sets) have been in operation for one year, </span><span style='font-family:"Avenir Next","serif";color:black'>ICANN</span><span style='font-family:"Avenir Next","serif";color:#333333;background:white'> will organize a review that will examine the extent to which the introduction or expansion of gTLDs has promoted competition, consumer trust and consumer choice …. </span><span style='font-family:"Avenir Next","serif";color:black'>ICANN</span><span style='font-family:"Avenir Next","serif";color:#333333;background:white'> will organize a further review of its execution of the above commitments two years after the first review, and then no less frequently than every four years. </span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div></blockquote><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt'><span style='font-family:"Avenir Next","serif";color:black'> In the Initial Draft Proposal, this AoC language was transposed into the Core Values by requiring ICANN to depend “on market mechanisms to proote and sustain a healthy competitive environment in the DNS market that enhances consumer trust and choice.” (Para 107, page 27 Initial Draft Proposal)</span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt'><span style='font-family:"Avenir Next","serif";color:black'> In the 2nd Draft Proposal we elected to delete the reference to consumer trust in the Mission statement and include it in the Review section of the Bylaws (See 3rd Report, Appendix 9, Para. 33). The reason we agreed to make this switch was because it is not a standalone ICANN commitment in the AoC, rather, it is specifically tied to new gTLD expansion and specifically tied to a required review. </span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt'><span style='font-family:"Avenir Next","serif";color:black'> Several commenters in both the 2nd and 3rd comment round argued that the Core Values should specifically call out consumer trust. Some have disputed my characterization of Paragraph 3 of the AoC (i.e., it states the goals of the AoC but does not recite a specific commitment), on the grounds that my characterization is an opinion and not a fact. </span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt;line-height:120%'><b><span style='font-family:"Avenir Next","serif";color:black'>QUESTIONS:</span></b><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt;line-height:120%'><span style='font-family:"Avenir Next","serif";color:black'>Should an AoC provision specific to TLD expansion be leveraged to impose generalized, independent, and affirmative competition and consumer trust protection obligations on ICANN?</span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><p class=MsoNormal style='text-indent:-27.35pt'><span style='font-family:"Avenir Next","serif";color:black'>Does ICANN’s fundamental Mission to ensure “stable and secure operation” of the DNS, and its various Commitments (i.e., to use processes that enable competition, and to preserve stability, reliability, security, global interoperability, resilience, and openness) adequately address this concern? </span><span style='font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt'><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><blockquote style='margin-left:30.0pt;margin-right:0cm'><div style='margin-left:27.35pt;margin-top:12.0pt;margin-bottom:6.0pt'><p class=MsoNormal style='text-indent:-27.35pt'><span style='font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div></blockquote></div><div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p></div><p class=MsoNormal style='margin-top:12.0pt;mso-margin-bottom-alt:auto'><b><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:black'>J. Beckwith Burr</span></b><b><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#3366FF'><br></span></b><b><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#008656'>Neustar, Inc.</span></b><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#7D7D7D'>/</span><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#7D7D7D'>Deputy General Counsel & Chief Privacy Officer<br>1775 Pennsylvania Avenue NW, Washington D.C. 20006</span><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:gray'><br></span><b><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#008656'>Office:</span></b><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#7D7D7D'>+1.202.533.2932 </span><b><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#008656'>Mobile:</span></b><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#7D7D7D'>+1.202.352.6367 </span><strong><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:#7D7D7D'>/</span></strong><span style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><a href="http://www.neustar.biz"><b><span style='font-size:9.0pt;color:#008656'>neustar.biz</span></b></a><o:p></o:p></span></p></div></div></div></div></body></html>