<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I agree that we need to remove the “every effort” language, which is indeed a loophole.. A rationale should be provided by the AC. Period. Next issue.<div class=""><br class=""></div><div class="">Thanks,</div><div class="">Robin</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 18, 2016, at 10:31 AM, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" class="">gregshatanipc@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:verdana,sans-serif">Mathieu,<br class=""><br class=""></div><div class="gmail_default" style="font-family:verdana,sans-serif">That recommendation ("every effort") is inadequate and frankly, bizarre. Under what circumstances could an AC make "every effort" and still fail to provide a rationale? If an AC makes "every effort" to develop a rationale and still fails, what does that tell us about the recommendation? That no rational support can be found for it? That the AC can agree on the result but not the rationale? That the AC would rather not state the rationale?</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br class=""></div><div class="gmail_default" style="font-family:verdana,sans-serif">For those who say that the GAC already offers rationales for their recommendations -- if those rationales were considered satisfactory, this issue would not have been raised in the first place. If necessary, we can go back to specific items of advice, and the rationales or lack thereof; but I don't know that we have the time to engage in such an exercise. For one, I recall that in the .africa IRP concerns were raised about the lack of a sufficiently-stated rationale. If the GAC is looking for greater parity with GNSO PDP policy recommendations, the documentation accompanying those recommendations should serve as a guide.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br class=""></div><div class="gmail_default" style="font-family:verdana,sans-serif">It is heartening to hear that the GAC is already working on improving their communication the rationales for their advice. As such, we all seem to be moving in the same direction.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br class=""></div><div class="gmail_default" style="font-family:verdana,sans-serif">With that in mind, there should be no real issue with removing the squishy "every effort" loophole and stating an unqualified requirement for a rationale for all AC advice.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br class=""></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Jan 18, 2016 at 11:17 AM, Steve DelBianco <span dir="ltr" class=""><<a href="mailto:sdelbianco@netchoice.org" target="_blank" class="">sdelbianco@netchoice.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap: break-word; font-size: 16px; font-family: Calibri, sans-serif;" class="">
<div class="">
<div class="">Mathieu — Regarding formal advice from any Advisory Committee (AC), many commenters reiterated that a rationale should be a
<u class="">requirement</u> for advice to be considered by the board. (BC, NPOC, Google, USCIB, RySG, Valideus, the US Chamber, RrSG, NCUC, I2C, Intel, IPC)</div>
<div class=""><br class="">
</div>
<div class="">It’s not enough to require that each AC "will make every effort”. </div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</div>
<div class=""><br class="">
</div>
<span class="">
<div style="font-family: Calibri; font-size: 12pt; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class="">
<span style="font-weight:bold" class="">From: </span><<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank" class="">accountability-cross-community-bounces@icann.org</a>> on behalf of Mathieu Weill <<a href="mailto:mathieu.weill@afnic.fr" target="_blank" class="">mathieu.weill@afnic.fr</a>><br class="">
<span style="font-weight:bold" class="">Date: </span>Monday, January 18, 2016 at 3:10 AM<br class="">
<span style="font-weight:bold" class="">To: </span>Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank" class="">gregshatanipc@gmail.com</a>>, Mike Chartier <<a href="mailto:mike.s.chartier@intel.com" target="_blank" class="">mike.s.chartier@intel.com</a>><br class="">
<span style="font-weight:bold" class="">Cc: </span>"<a href="mailto:accountability-cross-community@icann.org" target="_blank" class="">accountability-cross-community@icann.org</a>" <<a href="mailto:accountability-cross-community@icann.org" target="_blank" class="">accountability-cross-community@icann.org</a>><br class="">
<span style="font-weight:bold" class="">Subject: </span>Re: [CCWG-ACCT] DOCUMENT - Rec 11 - GAC Advice (first reading)<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">
<div lang="FR" link="blue" vlink="purple" class="">
<div class=""><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="">Mike,
<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="">Good catch indeed. Precisely the point of our first reading exercise.
<u class=""></u><u class=""></u></span></p><span class=""><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="">So we will add this to recommendation 11 agenda item tomorrow.
<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="">I will note that the current annex includes a related recommendation :
<u class=""></u><u class=""></u></span></p><p style="margin-left:40.0pt" class="">
<span lang="EN-US" class=""><span class="">·<span style="font-style:normal;font-variant:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'" class="">
</span></span></span><span lang="EN-US" class="">Insert a mention for all ACs: “The AC will make every effort to ensure that the advice provided is clear and supported by a rationale.”<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="">Best,<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="">Mathieu<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class=""><u class=""></u> <u class=""></u></span></p>
</span><p class="MsoNormal"><b class=""><span style="font-size:10pt;font-family:Tahoma,sans-serif" class="">De :</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif" class="">
<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank" class="">accountability-cross-community-bounces@icann.org</a> [<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank" class="">mailto:accountability-cross-community-bounces@icann.org</a>]
<b class="">De la part de</b> Greg Shatan<span class=""><br class="">
<b class="">Envoyé :</b> lundi 18 janvier 2016 05:30<br class="">
<b class="">À :</b> Chartier, Mike S<br class="">
<b class="">Cc :</b> <a href="mailto:accountability-cross-community@icann.org" target="_blank" class="">accountability-cross-community@icann.org</a><br class="">
</span><b class="">Objet :</b> Re: [CCWG-ACCT] DOCUMENT - Rec 11 - GAC Advice (first reading)<u class=""></u><u class=""></u></span></p><span class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p>
<div class="">
<div class=""><p class="MsoNormal"><span style="font-family:Verdana,sans-serif" class="">Mike,<u class=""></u><u class=""></u></span></p>
</div>
<div class=""><p class="MsoNormal"><span style="font-family:Verdana,sans-serif" class=""><u class=""></u> <u class=""></u></span></p>
</div>
<div class=""><p class="MsoNormal"><span style="font-family:Verdana,sans-serif" class="">Good point and good catch. This should not have been overlooked.<u class=""></u><u class=""></u></span></p>
</div>
<div class=""><p class="MsoNormal"><span style="font-family:Verdana,sans-serif" class=""><u class=""></u> <u class=""></u></span></p>
</div>
<div class=""><p class="MsoNormal"><span style="font-family:Verdana,sans-serif" class="">Greg<u class=""></u><u class=""></u></span></p>
</div>
</div>
</span><div class=""><p class="MsoNormal"><u class=""></u> <u class=""></u></p>
<div class=""><span class=""><p class="MsoNormal">On Sun, Jan 17, 2016 at 9:52 PM, Chartier, Mike S <<a href="mailto:mike.s.chartier@intel.com" target="_blank" class="">mike.s.chartier@intel.com</a>> wrote:<u class=""></u><u class=""></u></p>
</span><div class="">
<div class=""><span class=""><p class=""><span lang="EN-US" class="">I think this is another illustration of how we need to be careful in documenting the process for handling comments (other than the Boards). For Recommendation 11 several commenters offered the proposal to add a requirement for GAC advice
to be accompanied by a rationale. Given the general acceptance of proposals for rationales in other areas, I would have thought it would have at least been given a note in the prep document.<u class=""></u><u class=""></u></span></p><p class=""><span lang="EN-US" class="">Look forward to discussing on Tues.<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class=""> </span><span lang="EN-US" class=""><u class=""></u><u class=""></u></span></p><p class="MsoNormal"><a name="1902890098_-729495936__MailEndCompose" class=""><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class=""> </span></a><span lang="EN-US" class=""><u class=""></u><u class=""></u></span></p>
</span><div class="">
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm" class=""><p class="MsoNormal"><b class=""><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif" class="">From:</span></b><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif" class=""><a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank" class="">
accountability-cross-community-bounces@icann.org</a> [mailto:<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank" class="">accountability-cross-community-bounces@icann.org</a>]
<b class="">On Behalf Of </b>Alice Jansen<br class="">
<b class="">Sent:</b> Friday, January 15, 2016 12:01 PM<br class="">
<b class="">To:</b> <a href="mailto:accountability-cross-community@icann.org" target="_blank" class="">
accountability-cross-community@icann.org</a><br class="">
<b class="">Subject:</b> [CCWG-ACCT] DOCUMENT - Rec 11 - GAC Advice (first reading)</span><span lang="EN-US" class=""><u class=""></u><u class=""></u></span></p>
</div>
</div>
<div class="">
<div class=""><span class=""><p class="MsoNormal"><span lang="EN-US" class=""> <u class=""></u><u class=""></u></span></p>
<div class="">
<div class="">
<div class=""><p class="MsoNormal"><u class=""><span lang="EN-US" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">Sent on behalf of CCWG-ACCT Co-Chairs</span></u><span lang="EN-US" class=""><u class=""></u><u class=""></u></span></p>
</div>
</div>
</div>
</span><div class="">
<div class="">
<div class="">
<div class="">
<div class=""><p class="MsoNormal"><span lang="EN-US" style="font-size: 9pt; font-family: Arial, sans-serif;" class=""> </span><span lang="EN-US" class=""><u class=""></u><u class=""></u></span></p>
</div>
<div class=""><p class="MsoNormal"><span lang="EN-US" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">In preparation for your R<i class="">ecommendation 11 – GAC Advice (first reading)</i> discussion
scheduled for your call #78 - Tuesday, 19 January 2016 (12:00 – 15:00 UTC) - please find attached the material to review. </span><span lang="EN-US" class=""><u class=""></u><u class=""></u></span></p>
</div><span class="">
<div class=""><p class="MsoNormal"><span lang="EN-US" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">Please use this email thread to circulate any comments you may have in advance of the call.</span><span lang="EN-US" class=""><u class=""></u><u class=""></u></span></p>
</div>
<div class=""><p class="MsoNormal"><span lang="EN-US" style="font-size: 9pt; font-family: Arial, sans-serif;" class=""> </span><span lang="EN-US" class=""><u class=""></u><u class=""></u></span></p>
</div>
<div class=""><p class="MsoNormal"><span lang="EN-US" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">Thank you</span><span lang="EN-US" class=""><u class=""></u><u class=""></u></span></p>
</div>
<div class=""><p class="MsoNormal"><span lang="EN-US" style="font-size: 9pt; font-family: Arial, sans-serif;" class=""> </span><span lang="EN-US" class=""><u class=""></u><u class=""></u></span></p>
</div>
<div class=""><p class="MsoNormal"><span lang="EN-US" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">Mathieu, Thomas, León</span><span lang="EN-US" class=""><u class=""></u><u class=""></u></span></p>
</div>
</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div><p class="MsoNormal" style="margin-bottom:12.0pt"><span class=""><br class="">
_______________________________________________<br class="">
Accountability-Cross-Community mailing list<br class="">
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank" class="">Accountability-Cross-Community@icann.org</a><br class="">
</span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><u class=""></u><u class=""></u></p>
</div><p class="MsoNormal"><u class=""></u> <u class=""></u></p>
</div>
</div>
</div>
</div>
</span>
</div>
</blockquote></div><br class=""></div>
_______________________________________________<br class="">Accountability-Cross-Community mailing list<br class=""><a href="mailto:Accountability-Cross-Community@icann.org" class="">Accountability-Cross-Community@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community<br class=""></div></blockquote></div><br class=""></div></body></html>