<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)"><style><!--
/* Font Definitions */
@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:11.0pt;
font-family:"Calibri",sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.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:12.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.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.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
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.apple-converted-space
{mso-style-name:apple-converted-space;}
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-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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:1741519116;
mso-list-type:hybrid;
mso-list-template-ids:2146233734 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1896970235;
mso-list-template-ids:1601459452;}
@list l1:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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=blue vlink=purple><div class=WordSection1><p class=MsoPlainText><span style='font-size:12.0pt'>Dear Work Track 5 members,</span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'>Please see below the action items and notes from the meeting today (08 August). <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, which will be posted on the wiki.</i> </span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>See also the attached the referenced slides, draft recommendations, and path to initial report.<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'>Kind regards,</span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'>Julie</span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'>Julie Hedlund, Policy Director</span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'>----------------------------------------------------------------------------------------------------------------------------------</span><o:p></o:p></p><p class=MsoPlainText><b><span style='font-size:12.0pt'>Notes/Action Items:</span></b><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoPlainText><b><span style='font-size:12.0pt'>Action Items:</span></b><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoPlainText>ACTION ITEM 1: Re: Recommendations on Country and Territory Names: Work Track 5 members should review the recommendations and indicate support or objections.<o:p></o:p></p><p class=MsoPlainText>ACTION ITEM 2: Re: Non-AGB Terms: Work Track 5 members should continue to send concrete proposals to the list.<o:p></o:p></p><p class=MsoPlainText><span style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:12.0pt'>Notes:</span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal>1. Welcome/Agenda Review/SOI Updates: No SOI Updates<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2. Review of Consensus Call Process and Work Plan:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Slide 5: Consensus Call Process<o:p></o:p></p><p class=MsoNormal>Slide 6: More on the Consensus Call Process<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Discussion:<o:p></o:p></p><p class=MsoNormal>-- On slide 5 there is an internal contradiction -- strong support/significant opposition: not sure what that is.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Emily Barabas: Strong support but significant opposition - a position where, while most of the group supports a recommendation, there are a significant number of those who do not support it.<o:p></o:p></p><p class=MsoNormal>Steve Chan: There is a typo. It should be Strong Support BUT Strong Opposition.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-- Question: Will there be opportunity to comment before the document goes for public comments? Answer: In your deliberations you all will have plenty of opportunity to comment on the text.<o:p></o:p></p><p class=MsoNormal>-- This is part of the temperature taking of the WT5 members -- to know where we are at. Consensus is not a vote.<o:p></o:p></p><p class=MsoNormal>-- Hope is to develop a draft of the initial report and have progress to show by the Barcelona meeting.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Work Track 5 -- Path to Initial Report:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-- Concerns about meeting the schedule; that it is too ambitious.<o:p></o:p></p><p class=MsoNormal>-- Schedule allows for time for public comments on the initial report and for the recommendations to be pulled into the full WG report.<o:p></o:p></p><p class=MsoNormal>-- This is a timeline and it may change.<o:p></o:p></p><p class=MsoNormal>-- WTs 1-4 also are under pressure, not just WT5, to complete their work.<o:p></o:p></p><p class=MsoNormal>-- This is in line with our announced plans, but is perhaps a bit more specific.<o:p></o:p></p><p class=MsoNormal>-- We are not under pressure of the other WTs, we are under our own pressure.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>From the chat:<o:p></o:p></p><p class=MsoNormal>Jorge Cancio (GAC Switzerland) 2: As said on list the workplan seems very ambitious, probably too ambitious in terms of timing. The GAC recalled in its Panama Communique that “several GAC members expressed concern that the timeline for this work should allow for the complexity and sensitivity of many of the issues.”<o:p></o:p></p><p class=MsoNormal>Kavouss Arasteh: Jorje +1<o:p></o:p></p><p class=MsoNormal>Thiago Jardim: +1 Jorge. These concerns were not just communicated in Panama, but also prior to that, in San Juan, and in between the two meetings, through GAC input to WT 5.<o:p></o:p></p><p class=MsoNormal>Cheryl Langdon-Orr (CLO PDP Co Chair): This is well noted Jorge the whole PDP is working at ambitious time lines and WT5 is trying its best to integrate and allow for key discussions to occur if at all possible at ICANN63, we trust that will aid GAC not hibder it<o:p></o:p></p><p class=MsoNormal>Kavouss Arasteh: We do not want the pressure be put on WT5 while other wtS WTs be given more flexibility to complete their works afterward<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>3. Consensus Call on Country and Territory Names<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Slide 9: Country and Territory Names and Initial Consensus Designations on Policy Recommendations:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Discussion:<o:p></o:p></p><p class=MsoNormal>-- The recommendations only pertain to country and territory names.<o:p></o:p></p><p class=MsoNormal>-- Question: Are we talking about other languages/scripts that are not listed -- how will we know unless we create finite lists? Answer: We are trying to point to a finite list, such as the list of UN languages.<o:p></o:p></p><p class=MsoNormal>-- The UN language is a way because we know what they are, but other countries may have problems with that. <o:p></o:p></p><p class=MsoNormal>-- Important procedural point: no factual basis for making the change (on languages) so keep as is in 2012 AGB.<o:p></o:p></p><p class=MsoNormal>-- UN languages is very limited. Official languages exists only in certain jurisdictions.<o:p></o:p></p><p class=MsoNormal>-- In Switzerland we have 4 official languages, but we have many other languages that are very relevant to important communities.<o:p></o:p></p><p class=MsoNormal>-- Any strong objections to keeping "in any language" from the 2012 AGB? [Several objections entered into the chat.]<o:p></o:p></p><p class=MsoNormal>-- UN official language has political background back to 1945.<o:p></o:p></p><p class=MsoNormal>-- Strong objections to "in any language" text. Would be interested to know how it got in there.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>From the chat:<o:p></o:p></p><p class=MsoNormal>Kristina Rosette (Amazon Registry): It would be really helpful if these slides would state, at the outset, if the draft recommendations diverge from the 2012 AGB and highlight how they do.<o:p></o:p></p><p class=MsoNormal>Carlos Gutierrez: General Comment on this consensus call on the Aug 8 draft document - #1. I miss the objective measuring consensus on a document that has no specific recommendation on the possible inclusion or MORE geographic name in any eventual subsequent rounds. For me, the draft for discussion BLOCKS any chance for geographic names to geo beyond the 2012 AGB. This is not more consensus call on the status quo. In my view it does NOT reflect the full discussions to date. Neither do the so called recommendations seem to be in the spirit of improving the 2012 AGB. My suggestion is to work around the final section of each recommendation and either make a positive WT5 recommendation out of it, or accept that there is no coherent recommendation from the WT5<o:p></o:p></p><p class=MsoNormal>Carlos Gutierrez: General Comment on this consensus call on the Aug 8 draft document - #2. As I have noted my written comments to the draft recommendations on the list, I want to restate my comment that the drafting style in which the present so called "recommendations" do not fully reflect neither the full range of the deliberations nor all the group input as per the GNSO consensus call rules <quote> Draft recommendations "based on deliberations" and group input <unquote>, The only segment of each of the proposed recommendations that gets close to a real recommendation avoids taking responsibility for the substance of the recommendation, by suggestion to send the issue back to the community without any procedural consideration. This style of recommendations is foreign to the GNSO council past experience and sending the issue back to the “community” makes the whole effort to look rather void in my view. <o:p></o:p></p><p class=MsoNormal>Jorge Cancio (GAC Switzerland) 2: As mentioned on list, regarding the draft recommendation 1: shouldn’t there be a mention that letter-character or character-character combinations confusingly similar with a 2 letter country code should be avoided? (I think I heard this during the discussions on the issue…)<o:p></o:p></p><p class=MsoNormal>Adrian Carballo: +1 to Jorge´s comments <o:p></o:p></p><p class=MsoNormal>Jorge Cancio (GAC Switzerland) 2: question: what is the rationale for the limitation to official an UN languages?<o:p></o:p></p><p class=MsoNormal>Emily Barabas: @Kristina, the "hollow" bullets identify where there is divergence<o:p></o:p></p><p class=MsoNormal>Kristina Rosette (Amazon Registry): @Emily: Thanks, but I think it's helpful to state at the outset if there is divergence, especially because "consistent with" is not the same as "identical to." Just trying to make sure there's no uncertainty later about whether everyone knew and understood how the recs differ from AGB 2012.<o:p></o:p></p><p class=MsoNormal>Jorge Cancio (GAC Switzerland) 2: "official language" may be very tricky, as there is no official determination in many countries - nevertheless the language may be widely used and/or relevant<o:p></o:p></p><p class=MsoNormal>Emily Barabas: Understood. Would it be helpful to do a redline of the AGB text itself?<o:p></o:p></p><p class=MsoNormal>Kristina Rosette (Amazon Registry): I defer to our GAC colleagues here, but I thought that identification of official language and scripts could be potentially contentious.<o:p></o:p></p><p class=MsoNormal>Kristina Rosette (Amazon Registry): @Emily: yes, very. thank you!<o:p></o:p></p><p class=MsoNormal>Jorge Cancio (GAC Switzerland) 2: Please read my comments in the chat out: as long as there is no factual basis for the limitation in languages I would tend to object to that change v-a-v the 2012 AGB<o:p></o:p></p><p class=MsoNormal>Jorge Cancio (GAC Switzerland) 2: instead of "official" we could talk about "official and relevant languages"<o:p></o:p></p><p class=MsoNormal>Edmon: it is possible to develop a list that can be updated from time to time... yes... so "finite" doesnt mean a particular max number need to be identified<o:p></o:p></p><p class=MsoNormal>Jorge Cancio (GAC Switzerland) 2: why is it unworkable - what is the factual basis for saying that?<o:p></o:p></p><p class=MsoNormal>christopher wilkinson: I agree with Greg on finite lists of all appliccable and official langues and scriopts.<o:p></o:p></p><p class=MsoNormal>Ashley Heineman: Jorge - are you indicating that *all* languages need to be included? <o:p></o:p></p><p class=MsoNormal>Kavouss Arasteh: Jorge +1<o:p></o:p></p><p class=MsoNormal>Jorge Cancio (GAC Switzerland) 2: all relevant languages for sure... <o:p></o:p></p><p class=MsoNormal>Edmon: UN languages only may serve as a starting point... but probably should not be the upperbound<o:p></o:p></p><p class=MsoNormal>christopher wilkinson: +pt.<o:p></o:p></p><p class=MsoNormal>Ashley Heineman: Jorge, thanks for clarifying. That is much more reasonable. <o:p></o:p></p><p class=MsoNormal>Adrian Carballo: +1 to Jorge´s comments about languages<o:p></o:p></p><p class=MsoNormal>Dessalegn Yehuala: Correct there are no UN official languages but there are UN working languages<o:p></o:p></p><p class=MsoNormal>Greg Shatan: I object to the “any language” standard.<o:p></o:p></p><p class=MsoNormal>Dessalegn Yehuala: Correct there are no UN official languages but there are UN working languages<o:p></o:p></p><p class=MsoNormal>Greg Shatan: I object to the “any language” standard.<o:p></o:p></p><p class=MsoNormal>Edmon: relevant languages? (undersatnd that "relevant" is vague but might strike a balance at this level for now)<o:p></o:p></p><p class=MsoNormal>Susan Payne: I object too. how is an applicant to know? how many languages even are there? <o:p></o:p></p><p class=MsoNormal>Alberto Soto: +1 Greg<o:p></o:p></p><p class=MsoNormal>Paul McGrady: Hi Susan, I saw somewhere that there are 6,500+ languages in the world.<o:p></o:p></p><p class=MsoNormal>Kristina Rosette (Amazon Registry): I also object to the "any language" standard.<o:p></o:p></p><p class=MsoNormal>Jorge Cancio (GAC Switzerland) 2: a country name is highly sensitive - that is why UN and "official" is not enough... "all languages" may not be necessary, but we need a middle ground there<o:p></o:p></p><p class=MsoNormal>Greg Shatan: You asked for fact-based arguments, not for prior historical occurrences.<o:p></o:p></p><p class=MsoNormal>Jorge Cancio (GAC Switzerland) 2: but Greg, we should learn from past experience and not resolve just theoretical problems - but I'm in if we look for a middle-ground<o:p></o:p></p><p class=MsoNormal>Kavouss Arasteh: If you want to retain reference to UN official language, we may preceede that by"including but not limited " to read including but not limited to UN official language <o:p></o:p></p><p class=MsoNormal>Ashley Heineman: I think it goes both ways Jorge. Is their a proven need to include all languages spoken in a country?<o:p></o:p></p><p class=MsoNormal>Greg Shatan: I’m happy to look at past experiences as well, but that shouldn’t be used to shut off reasoned analysis.<o:p></o:p></p><p class=MsoNormal>Greg Shatan: Good question, Ashley. I look forward to @Jorge’s response.<o:p></o:p></p><p class=MsoNormal>Cheryl Langdon-Orr (CLO PDP Co Chair): Perhaps take that last paragrapgh ou tto the list between now and our next call then...<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Recommendation 1:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Discussion:<o:p></o:p></p><p class=MsoNormal>-- Question: In bullet 1, third line -- is it two letter-letter character? Could character not be a letter? Answer: It is letter-letter combinations. The word "character" might sound broad, but it is letter-letter (not other characters). The quote from the 2012 AGB talks about two-character ascii strings -- only gTLDs had to be three or more characters. This is a subset of the text from 2012. That is why the term "character" is used as from the quote from the AGB.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>From the chat:<o:p></o:p></p><p class=MsoNormal>Dessalegn Yehuala: the WT5 is about goegraphic and territory names at the top level, and existing label generation rules prevent top level names having digits.<o:p></o:p></p><p class=MsoNormal>Jorge Cancio (GAC Switzerland) 2: I have repeatedly made a comment on letter-character combinations that might be similar to two-letter country codes - please consider it...<o:p></o:p></p><p class=MsoNormal>Steve Chan: @Jorge, you made a comment about ensuring that if letter-digit strings end up being recommended, that they are not confusingly similar to existing ccTLDs. At least in 2012, string similarity took into account all existing TLDs, including ccTLDs, so your concern would seem to be addressed?<o:p></o:p></p><p class=MsoNormal>Jorge Cancio (GAC Switzerland) 2: @Steve: that should be referred to at least in the draft recommendation so that it is transparent<o:p></o:p></p><p class=MsoNormal>Kristina Rosette (Amazon Registry): For clarity, I suggest a slight revision to the recommendation, with suggested change in ALL CAPS: "The Work Track recommends reserving AT THE TOP LEVEL all two-character . . . .<o:p></o:p></p><p class=MsoNormal>Heather Forrest: +1 to Kristina Rosette's drafting recommendation<o:p></o:p></p><p class=MsoNormal>Steve Chan: Just to reiterate and as Edmon and Alexander mentioned in the chat, digits were disallowed in 2012.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Recommendation 2:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Discussion:<o:p></o:p></p><p class=MsoNormal>-- Delete the final paragraph -- isn't that what the WT5 should be doing? ("The ICANN community may want to consider whether a future process shoudl be established...") Should include at least a process outline.<o:p></o:p></p><p class=MsoNormal>-- The references to the 2007 policy is misleading.<o:p></o:p></p><p class=MsoNormal>-- This is a continuation of the GNSO policy recommendation process.<o:p></o:p></p><p class=MsoNormal>-- Agree with redrafting last paragraph.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>From the chat:<o:p></o:p></p><p class=MsoNormal>Edmon: on the sentence on "future process" perhaps we need to think about whether this working group can take on that "future process".. if so, then we can simply ether do so or add "this working group" in the last sentence of rec #2<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>4. Wrap Up - Non-AGB Terms<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Slide 11: Non-AGB Terms -- start discussion on the mailing list.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-- Apache helicopter is a great hypothetical. Example of this sort of thing can be handled by national or local legislation.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>5. AOB: New Telecom Provider<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Slide 13: WT5 is Getting a New Telecom Provider:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-- Check carefully invites for the upcoming meeting.<o:p></o:p></p><p class=MsoNormal>-- The number will change and the interaction is different -- passcode is 4 digit, and you must record our name.<o:p></o:p></p><p class=MsoNormal>-- Adobe Connect is still available. <o:p></o:p></p></div></body></html>