<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 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle34
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle35
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle36
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle37
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle38
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle39
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle40
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle41
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle43
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle44
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle45
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle46
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle47
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle48
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle49
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle50
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle51
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle52
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle53
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle54
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle55
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle56
{mso-style-type:personal-reply;
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 lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">Thanks Julie – re the possible high level agreement in relation to requirements for GAC Advice, the “friendly amendment” to the proposed language was to state the requirement for a rationale
as being based on (i) law “and</span><span style="font-size:12.0pt;color:red">/or”</span><span style="font-size:12.0pt;color:#1F497D"> (ii) public policy. I think this addition of the “or” (as noted by Steve in the document) would be important since the
ICANN ByLaws make no reference to the GAC needing to cite any particular law in its Consensus public policy advice to the Board. Separately, I agree with those who noted that this proposed provision would read better if the
</span><span style="font-size:12.0pt;color:#C00000">word “must” were changed to “should”.</span><span style="font-size:12.0pt;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">It may also be appropriate to note that if the WG’s proposed high level agreement as to GAC Advice is in fact adopted by the Board (if recommended by GNSO Council and over the objection of the
GAC), this would likely require amendment to the ByLaws so the WG may want to be specific about that . In this regard, I recall a lot of discussion in the Accountability workstream regarding the definition of “GAC Consensus Advice”. That definition appears
below. (Greg Shatan may have a clearer recollection of this discussion than I do.)
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">What gets VERY interesting here is that the Board overriding GNSO policy advice requires a 2/3 majority and the Board overriding GAC Advice requires a 60% majority vote (which I think is 11 Directors).
So the WG should be cognizant that we may be setting up a stalemate at the Board level on these issues that could well result in the Board coming back to the GNSO and the GAC and telling us all to “work it out”. The problem there, of course, is possible further
delay in the next round so I think the WG has to consider whether engagement for that purpose is advisable, as will GNSO Council once it receives the Final Report of the WG. A “fallback” position would be to develop language that does not require ByLaws amendments
and would not put the Board in the “Dueling ByLaws” bottleneck, unless of course that is exactly what the WG as a whole recommends that we trigger. (So again, it may be appropriate to seek public comment on that particular issue.)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">Would it not be better to state the “high level agreement” in the form of recommending that the Board formally request a written statement from the GAC as to its rationale? (That recommendation
would not necessarily put the Board in the position of having to amend ByLaws and would not necessarily create a “bottleneck”.) In other words, it would be much easier for the Board to adopt. Could we say as follows:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">"<span style="color:#C00000">The WG recommends that the Board formally request that GAC Consensus Advice</span> include a clearly articulated
<span style="color:#C00000">written </span>rationale, including the (i) national or international law; and<span style="color:#C00000">/or
</span> (ii) merits-based public policy reasons, upon which it is based."</span><span style="font-size:12.0pt;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">The new ByLaws section on GAC Advice from the 2016 Accountability Process in Sec 12.2.(a) is:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><img width="970" height="908" style="width:10.1041in;height:9.4583in" id="Picture_x0020_1" src="cid:image001.png@01D57216.147E82E0"><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org>
<b>On Behalf Of </b>Julie Hedlund<br>
<b>Sent:</b> Monday, September 23, 2019 12:11 PM<br>
<b>To:</b> gnso-newgtld-wg@icann.org<br>
<b>Subject:</b> [Gnso-newgtld-wg] Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 23 September 2019<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">[EXTERNAL]</span></strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear Working Group members,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Please see below the notes from the meeting on 23 September 2019.
<b><i>These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat,</i></b> which will be posted at:
<a href="https://community.icann.org/display/NGSPP/2019-09-23+New+gTLD+Subsequent+Procedures+PDP">
https://community.icann.org/display/NGSPP/2019-09-23+New+gTLD+Subsequent+Procedures+PDP</a>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Julie<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Julie Hedlund, Policy Director<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Notes and Action Items:</span></b><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt"> </span></b><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Actions:</span></b><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Objections -- re: GAC Advice<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Option listed in Initial Report: GAC Advice must include clearly articulated rationale, including the national or international law upon which it is based.</span></i><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">ACTION ITEM 1: Re: BRG/RySG: New Idea - Supports this option but suggests the language is modified to "GAC Advice must include clearly articulated rationale, including the (i) national or international law;
and (ii) merits-based public policy reasons, upon which it is based". <b>Review to determine if WG agrees to add to high-level agreements</b>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">ACTION ITEM 2: Re: INTA: New Idea - Require that GAC Advice nominate and provide contact details for an authorized GAC contact who is knowledgeable about the grounds for the objection and authorized to discuss
solutions with a view to trying to reach a resolution. <b>Review to determine if WG agrees to add to high-level agreements</b>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Option listed in Initial Report: Future GAC Advice, and Board action thereupon, for categories of gTLDs should be issued prior to the finalization of the next Applicant Guidebook. Any GAC Advice issued
after the application period has begun must apply to individual strings only, based on the merits and details of the application, not on groups or classes of applications.</span></i><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">ACTION ITEM 3: Review to determine if WG agrees to add to high-level agreements.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">ACTION ITEM 4: Look in the Bylaws with respect to GAC Advice.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Notes:</span></b><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">1. Updates to Statements of Interest: No updates provided.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">2. Review of summary documents:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- General Question: Where will we see the summary of agreements? Staff and Co-Chairs are working on a draft.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Consider capturing agreements with actions, but these would need to be specifically called out, ideally by leadership, so that they can be accurate captured.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">a. Objections -- See: <a href="https://docs.google.com/document/d/1BkRn9nYeBNjyx2mTw-3nIDn22jTumWd4w1PZR-KNrPs/edit?usp=sharing">
https://docs.google.com/document/d/1BkRn9nYeBNjyx2mTw-3nIDn22jTumWd4w1PZR-KNrPs/edit?usp=sharing</a>, continue discussion, start on page 5<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Opportunity to amend an application or add Public Interest Commitments in response to concerns raised in an objection
<u>(see High-Level Agreement E above)</u>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Noting opposition by NCSG to PICs. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Changes to applications went out for public comment, but voluntary PICs don’t make sense. Concerned about changes being presented in PICs, when they aren’t.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- What is the distinction between a change to an application versus one that is made in response to an objection? It is an agreement between ICANN and the applicant. There is still a role for ICANN in compliance
with what the applicant said what they would do.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- If part of the agreement is in a PIC then ICANN has the ability to outsource that compliance to a third party.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- The CPE is not an objection process, it’s an evaluation. There is no CPE objection process. We should not confuse Community Objections with Community Priority Evaluations. Community Objections come
from affected community members, the CPE aims if a community applicant fulfills the community criteria.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- There can be opposition to community applications, although that is not an objection.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Community Priority Evaluation rules and principles were not solidified before the application window closed in 2012. Don’t want the rules and principles to shift after the window closes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Let’s keep the Opposition / Objection separate.</span><span style="font-size:11.0pt;font-family:"MS Gothic"">
</span><span style="font-size:11.0pt">The Opposition component of CPE we will tackle when we
discuss CPE (2 topics from now). </span><span style="font-size:11.0pt;font-family:"MS Gothic"">
</span><span style="font-size:11.0pt">For today, lets focus ONLY on Community-based objections.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Objections filed by under Community Objections should be time-limited just as with other objections - String Confusion, Legal Rights, Limited Public Interest. CPE should not be used to "submit" opposition
akin to an objection.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- The assumption after reading the AGB was once a community applicant gets through objection and public comments that would be the basis for CPE, but that didn’t happen and allowed community opposition to
come in weeks before the application window closed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Additional comments on possible remediation measures in response to objections.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- ALAC comment: the WG policies will go to an Implementation Review Team. This is different from the recommendation for a Standing IRT, which is to address issues that arise after implementation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Were some objections in the 2012 round filed with the specific intent to delay the processing of applications for a particular string? How can this issue be addressed?:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Re: NSCG: Agreement - Working Group should build safeguards into the objection process that protect against potential gaming and other manipulations of the process. There is agreement to build in such safeguards.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Re: NTA: New Idea - Suggests quick look mechanisms, processes which would allow for summary judgments and costs awards in clear cut non-cases, as well as clear application guidelines for applicants and
clear conflicts of interest measures. Seems to be general agreement to this. Can we say who would be the third party to handle the quick look? For PICDRPs ICANN Org does it. For the limited public interest objection in the 2012 round it was a third party.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- From the AGB regarding the Limited Public Interest: The quick look is the Panel’s first task, after its appointment by the DRSP and is a review on the merits of the objection. The dismissal of an objection
that is manifestly unfounded and/or an abuse of the right to object would be an Expert Determination, rendered in accordance with Article 21 of the New gTLD Dispute Resolution Procedure.</span><span style="font-size:11.0pt;font-family:"MS Gothic"">
</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Should ICANN continue to fund all objections filed by the ALAC?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Re: Council of Europe: New Idea - Clarify ALAC’s task in the Bylaws. Can note this but can’t recommend changes to the Bylaws.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Need to clarify how the ALAC has standing to object. It’s more than standing. They were not given the privileges of the independent objector. For clarification, are there any limits to the number of
objections can file, if not there should be. Some comments supported that there should be limits.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Last time they had 3 objections to 1 string. ALAC filed 3 objections against .health. We have a stringent process within ALAC to get to filing an objection.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Limits should be qualitative, not quantitative. There already is a high bar for the ALAC to file objections.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- If you added a Global Public Interest standard, if the Board defines one, not sure why it would apply only to ALAC. The ALAC already applies the GPI standard.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">GAC Advice:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Option listed in Initial Report: GAC Advice must include clearly articulated rationale, including the national or international law upon which it is based.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Everyone except for the GAC agreed -- relying solely on the Bylaws for GAC advice.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Re: BRG/RySG: New Idea - Supports this option but suggests the language is modified to "GAC Advice must include clearly articulated rationale, including the (i) national or international law; and (ii) merits-based
public policy reasons, upon which it is based". <b>ACTION: Review to determine if WG agrees to add to high-level agreements</b>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Re: INTA: New Idea - Require that GAC Advice nominate and provide contact details for an authorized GAC contact who is knowledgeable about the grounds for the objection and authorized to discuss solutions
with a view to trying to reach a resolution. <b>ACTION: Review to determine if WG agrees to add to high-level agreements</b>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Presumably we cannot tell the GAC to change it's processes but we can make recommendations?</span><span style="font-size:11.0pt;font-family:"MS Gothic"">
</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- </span><span style="font-size:11.0pt;font-family:"MS Gothic"">
</span><span style="font-size:11.0pt">Language should say OR rather than "and" between the "(i) and the (ii).</span><span style="font-size:11.0pt;font-family:"MS Gothic"">
</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"MS Gothic"">
</span><span style="font-size:11.0pt">-- Perhaps it being a SHOULD instead of MUST ? Don't think GAC Advice has to be based on law so language would be "and/or" between (i) and (ii))<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Option listed in Initial Report: Future GAC Advice, and Board action thereupon, for categories of gTLDs should be issued prior to the finalization of the next Applicant Guidebook. Any GAC Advice issued after
the application period has begun must apply to individual strings only, based on the merits and details of the application, not on groups or classes of applications.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- Comments are in agreement.
<b>ACTION: Review to determine if WG agrees to add to high-level agreements</b>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">-- <b>ACTION: Look to the Bylaws with respect to GAC Advice.</b><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message
or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying
to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.
<br>
</font>
</body>
</html>