<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"><div>Dear DG Members,</div><div><br></div><div>Staff committed to sending additional materials that may inform the work of this group. Please review at your earliest convenience.</div><ul><li>In response to a GNSO Council resolution inviting the New gTLD Program Committee of the ICANN Board to provide input to the current and future gTLD application procedures, the ICANN Board passed the following resolution available here (<a href="https://www.icann.org/resources/board-material/resolutions-2014-11-17-en#2.b">https://www.icann.org/resources/board-material/resolutions-2014-11-17-en#2.b</a>). Contained within that resolution is Annex A, which highlights areas for possible policy work. <b>Staff recommends reviewing Annex A as it may spur discussion on issues missed by this group and the expansion or updating of already captured issues (<a href="https://www.icann.org/en/system/files/files/resolutions-annex-a-17nov14-en.pdf">https://www.icann.org/en/system/files/files/resolutions-annex-a-17nov14-en.pdf</a>).</b> </li><li>As there was some confusion about the process to request that the GNSO Council initiate an Issue Report, please consult the information available here: <a href="http://gnso.icann.org/en/node/31379/#Identification">http://gnso.icann.org/en/node/31379/#Identification</a>. As Marika mentioned on the call on 8 December, there is a set of information that is expected to be provided to allow the GNSO Council to make an informed decision. Within the PDP Manual, there is recommended format for a request for an Issue Report, which would certainly not prevent the DG from providing information beyond the recommended elements (template on page 2 - <a href="http://gnso.icann.org/en/council/annex-2-pdp-manual-16dec11-en.pdf">http://gnso.icann.org/en/council/annex-2-pdp-manual-16dec11-en.pdf</a>).</li></ul><div>Please feel free to discuss on list.</div><div><br></div><div>Best,</div><div><br></div><div><br></div><div><br></div><div><p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt;"><b><span style="font-size: 10pt; font-family: Arial, sans-serif;">Steven Chan</span></b><span style="font-size: 10pt; font-family: Arial, sans-serif;"><br>Sr. Policy Manager<br><br><b>ICANN<br></b>12025 Waterfront Drive, Suite 300</span></p><p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt;"><span style="font-size: 10pt; font-family: Arial, sans-serif;">Los Angeles, CA 90094-2536<br><a href="mailto:steve.chan@icann.org" title="blocked::mailto:karen.lettner@icann.org" style="color: blue;">steve.chan@icann.org<br></a><br>direct: +1.310.301.3886<br>mobile: +1.310.339.4410</span><o:p></o:p></p><p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt;"><span style="font-size: 10pt; font-family: Arial, sans-serif;">tel: +1.310.301.5800<o:p></o:p></span></p><p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt;"><span style="font-size: 10pt; font-family: Arial, sans-serif;">fax: +1.310.823.8649</span></p></div></body></html>