<html 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 name=Title content=""><meta name=Keywords content=""><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Calibri;}
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.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:12.0pt;
font-family:Calibri;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:542641036;
mso-list-type:hybrid;
mso-list-template-ids:2009786108 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body bgcolor=white lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:10.0pt'>Dear WG Members,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'>Staff would like to highlight a couple of specific items that were discussed on the full WG call on 10 January 20017, to both remind those that participated and to inform those that were unable to attend. The WG discussed the overarching issues in the context of the recently completed review of CC1. Resulting changes made to the associated deliberations/preliminary findings can be found here (<a href="https://docs.google.com/document/d/16Sd6mpO5MqHl7BHOl9HBENDgUvcqQ04QumbVNfVu-FM/edit?usp=sharing)">https://docs.google.com/document/d/16Sd6mpO5MqHl7BHOl9HBENDgUvcqQ04QumbVNfVu-FM/edit?usp=sharing)</a>. It was noted that additional work is needed on at least four of the overarching subjects, with the proposed action of soliciting WG volunteers to establish three drafting teams on:<o:p></o:p></span></p><p class=MsoListParagraph><span style='font-size:10.0pt'><o:p> </o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:10.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.0pt'>Different TLD Types<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:10.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.0pt'>Both Predictability and Community Engagement<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:10.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.0pt'>Applications Assessed in Rounds<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'>Please review the Google Doc to gather additional understanding about what these drafting teams would be expected to develop (WG members are also encouraged to make suggested changes to the Google Doc if they feel they are needed). The co-chairs ask that if there are any objections to the drafting team approach, that those concerns be voiced before the end of this week. Otherwise, the following week, volunteers will be sought and these drafting teams will be established to further these areas of work.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'>Best,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'>Steve<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='color:black'>From: </span></b><span style='color:black'><gnso-newgtld-wg-bounces@icann.org> on behalf of Julie Hedlund <julie.hedlund@icann.org><br><b>Date: </b>Tuesday, January 10, 2017 at 9:13 AM<br><b>To: </b>"gnso-newgtld-wg@icann.org" <gnso-newgtld-wg@icann.org><br><b>Subject: </b>[Gnso-newgtld-wg] Actions/Discussion Notes: New gTLD Subsequent Procedures PDP WG 10 January 2017<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Times New Roman"'><o:p> </o:p></span></p></div><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'>Dear WG Members,</span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'>Please see below the action items and discussion notes captured by staff from the meeting on 10 January. <i>These high-level notes are designed to help PDP WG members navigate through the content of the call and are not meant as a substitute for the transcript or recording</i>. The MP3, transcript, and chat room notes are provided separately and are posted on the wiki at: <a href="https://community.icann.org/display/NGSPP/1.+WG+Meetings"><span style='color:#0B4CB4'>https://community.icann.org/display/NGSPP/1.+WG+Meetings</span></a>.</span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'>Note that as there was extensive discussion in the chat room that is included for ease of reference below following the notes. Please also see the MP3 at: <a href="http://audio.icann.org/gnso/gnso-new-gtld-subsequent-10jan17-en.mp3">http://audio.icann.org/gnso/gnso-new-gtld-subsequent-10jan17-en.mp3</a>.</span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'>Best regards,</span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'>Julie</span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'>Julie Hedlund, Policy Director</span><o:p></o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Actions/Discussion Notes: New gTLD Subsequent Procedures PDP WG Meeting, 10 January</span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt'> </span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Action Item</span></b><span style='font-size:10.5pt'>: Ensure meeting invitations are sent out (specifically WT3 on 17 Jan and WT4 on 20 Jan, but review others). </span><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><i><span style='font-size:10.5pt'>1. WT Updates/CC2 Planning and Timeline</span></i><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- WT4: Rubens: WT4 next meeting is scheduled to Jan 19, but actual agenda is contingent on availability of experts (IDN, UA) to join the call; if one or both are we will focus on it, otherwise we will move towards CC2 questions.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Action Items:</span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>1. Leadership/staff will provide guidance about upcoming meeting topic scheduling.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>2. Leadership/staff will provide background materials prior to meetings taking place.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>CC2 Planning - Leadership to begin working on initial questions with their respective work track members.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><i><span style='font-size:10.5pt'>2. Categorization or Differentiation of gTLDs </span></i><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Context on edits in Google doc (from staff): Integrate the CC1 discussion input into this document.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:10.5pt'>Additional New gTLDs in the future:</span></u><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Additional new gTLDs in the future: [reading from the CC1 google doc]</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Be more explicit on changes in the document for people not the the call (policy on 2007).</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Good to say that what we are saying is not changing.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:10.5pt'>Categorization or differentiation of gTLDs: [reading from the CC1 Google Doc]</span></u><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Manipulation of categories -- concern about changing a category after the gTLD has been granted.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Need to identify the different categories and compliances. Need some enforcement mechanisms to make changes </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Could a community TLD change on the fly?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- I think they have a contract that binds them to the community.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- If the registry operator wanted to change their contract they could do so. Not sure that there is a mechanism now for when a registry operator goes beyond the scope of its agreement.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Spec 13...Some categories may need a special request and some might be what the brands have now</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- But it is not something without consequences.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:10.5pt'>Future new gTLDs assessed in 'rounds'</span></u><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Action Item:</span></b><span style='font-size:10.5pt'> The WG had agreed that at DT should document the issue, identify requirements, and propose a solution or solutions for consideration by the full WG.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- The point is that some have said that the allocation should be similar as to registrar accreditation and others disagreed. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- One thing that is missing is that the existence of the first round allowed us to extend the process to address unexpected issues that arose.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:10.5pt'>Predictability should be maintained or enhanced without sacrificing flexibility</span></u><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- No edits from previous.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:10.5pt'>Community engagement in new gTLD application process</span></u><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- No comments</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:10.5pt'>Limiting applications in total and/or per entity during an application window</span></u><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Not necessarily anticompetitive. Better to say that it is impractical.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- This has to be recorded. The reportage.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><b><u><span style='font-size:10.5pt'>AC Chat: </span></u></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Michelle DeSmyter:Dear All, Welcome to the New gTLD Subsequent Procedures Working Group call on Tuesday, 10 January 2017 at 03:00 UTC.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Michelle DeSmyter:Meeting page: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_aqjDAw&d=DgICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=ouIz7p_lZFhre3KdZnkf_0TQUMW7puZ6FaJudHRQuag&s=hfp5JwgSrNm8_CoG9au9h9YE6M6oKudjbRPh5xImxdg&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_aqjDAw&d=DgICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=ouIz7p_lZFhre3KdZnkf_0TQUMW7puZ6FaJudHRQuag&s=hfp5JwgSrNm8_CoG9au9h9YE6M6oKudjbRPh5xImxdg&e=</a></span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> John Laprise:Sound AOK</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jeff Neuman:Thanks</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Michael Flemming:I hope we have a good turnout </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Michael Flemming:yes I just had curry with chicken</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Michael Flemming:a place called coco's curry</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Kristina Rosette (Amazon Registry):Dialing in now</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Christa Taylor:I'm on Skype with her</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Cheryl Langdon-Orr (CLO):another reason to stick to UTC</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Christa Taylor:She's in the process of joining</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Kristina Rosette (Amazon Registry):Great. Am finishing dinner so on mute temporarily.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Philip Corwin:Happy new year to all</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Michael Flemming 2:Yes</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jeff Neuman:yes</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Michael Flemming 2:WT2 is also about a month behind at the current time. So we will be picking up the pace as much as possible.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jeff Neuman:i will go through that in a minute</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Rubens Kuhl:WT4 next meeting is scheduled to Jan 19, but actual agenda is contingent on availability of experts (IDN, UA) to join the call; if one or both are we will focus on it, otherwise we will move towards CC2 questions.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Emily Barabas:Next WT4 call: Thursday, 19 January 2017 at 15:00 UTC</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Cheryl Langdon-Orr (CLO):thx Emily </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Justine Chew:+1 on background and notes before meeting calls</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Justine Chew:Will help greatly to faciltate participation via email lists rather than attending calls at odd hours.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Christa Taylor:Good Summary Jeff!</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> avri doria:and contributing text suggestions and comments to the online drive docs helps too</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> avri doria:peopel can also suggest edits, thogh they can't finalize them.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> avri doria:i.e you can put proposed edits in.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Steve Chan:@Jeff, you had it right the first time :) Initial Report</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> John Laprise:Could staff please begin including a link to the wg page on the ICANN website in the calander announcement? It makes for navgation ease.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Steve Chan:@John, are you referring to the WIki page? If so, could we propose adding it to the agenda emails?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Rubens Kuhl:early</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Cheryl Langdon-Orr (CLO):sorry Team I am going to have leave early (now) for an offsite appointment... this is a last minute matter sorry again </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Kristina Rosette (Amazon Registry):Suggest the "no changes anticipated to existing policy" bullet be clarified in the doc to avoid confusion by those not on this call</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jeff Neuman:Thx Kristina......Steve, lets make the policy more explicit in the doc</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jeff Neuman:FYI, I added some things that Avri may read from the drive that did not make it in time for the pdf. Sorry</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Steve Chan:@Jeff, noted - was making some suggestions to Google Doc as you were speaking.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Michael Flemming 2:There are mechanisms for preventing abuse of contracttual changes that are preferential to categories like dotBrands.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jon Nevett:Communities are subject to Spec 12</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Karen Day:@Kristina wouldn't they lose thier spec 13 or spec 9 exemption only rather than have their RA cancelled?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Kristina Rosette (Amazon Registry):@Karen, you would think. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Kristina Rosette (Amazon Registry):correct, avri</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Karen Day:so, then you could in theory apply under one category and then "slide" to another</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jeff Neuman:@Karen - Yes for the brand TLD, they would not lose the TLD, but rather lose the exemptions. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jeff Neuman:That would mean having to do a Sunrise, etc.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Karen Day:by "another" I mean simply generic</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Kristina Rosette (Amazon Registry):@Karen: Same for Code of Conduct. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jeff Neuman:@Avri - can you turn up your mic?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jeff Neuman:17-7 Alabama up. mid 3rd quarter</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Sara Bockey:Roll Tide ;-)</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Karen Day:Not so fast @Sara - Tigers coming back!</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> John Laprise:+1 Avri</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jeff Neuman:good catch.....we will reword</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jeff Neuman:17-14 now</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Alan Greenberg:In the notes on my comment: ...extend the process to address unexpected issues that arose.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Jeff Neuman:@Avri - Let me know if you need some water and want me to take over :)</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Kristina Rosette (Amazon Registry):Thanks, Steve. Very helpful. Didn't want to book my flight only to discover that I was arriving a day too late</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Kristina Rosette (Amazon Registry):Great. thanks.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Christa Taylor:Thank-you!</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Karen Day:Goodnight all!</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Michael Flemming 2:Thank you!</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> Robin Gross:Bye all!</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p></div></body></html>