<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>I'm very proud of the URS subteams, whose work which went
      forward, in general, to appreciation and wide support in the full
      WG. Despite criticisms, this careful work was largely embraced by
      the WG and will be featured in our Initial Report -- with 34
      operational fixes and draft policy recommendations to be presented
      to the ICANN Community with support of the full WG.  <br>
    </p>
    <p>I hope we can replicate what worked well then.  If better
      guidance and agreement is needed, let's develop it. Frankly, I
      like the idea of smaller subteams and share the support that the
      efficiency of the subteam process is based in part on its smaller
      size and parallel processes... <br>
    </p>
    <p>Best, Kathy</p>
    <br>
    <div class="moz-cite-prefix">On 12/6/2018 11:44 AM, Jason Schaeffer
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:91333EFD3166714094B0A6DBE2E854E1015F11D96D@ESQWIRE-DC.esqwire.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Word 14 (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:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","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.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:12.0pt;
        font-family:"Times New Roman","serif";}
span.m8319100771079976775apple-converted-space
        {mso-style-name:m_8319100771079976775apple-converted-space;}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        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;}
/* List Definitions */
@list l0
        {mso-list-id:1067194210;
        mso-list-template-ids:1609085958;}
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]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">+1
            Georges.  
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">It’s
            neither helpful nor fair to attack the work of subgroup
            volunteers that spend the extra time and effort to research,
            review and bring a final work product back to the WG.   As I
            believe Susan and Cyntia expressed during yesterday’s call,
            its common and prudent business practice to delegate tasks.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We
            need to proceed and be efficient.    The WG has its role and
            the use of small teams that wish to go above and beyond
            should be respected as well.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Yes,
            we should have some better guidance and agreement on the
            treatment of the subteam work – as you say “the rules of the
            game.”    <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Parallel
            teams with a time that “works” is fair and efficient.   If
            one wishes to follow the work of both sub-teams that’s built
            in already.  
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In
            practice it’s also quite difficult for most to really
            dedicate the time to more than one subteam if we are going
            to be honest about the effort that’s really required.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
                Nahitchevansky, Georges
                [<a class="moz-txt-link-freetext" href="mailto:ghn@kilpatricktownsend.com">mailto:ghn@kilpatricktownsend.com</a>]
                <br>
                <b>Sent:</b> Thursday, December 06, 2018 11:23 AM<br>
                <b>To:</b> Jason Schaeffer; Michael Karanicolas; Julie
                Hedlund<br>
                <b>Cc:</b> gnso-rpm-wg<br>
                <b>Subject:</b> RE: [GNSO-RPM-WG] Actions & Notes:
                RPM PDP WG Meeting 05 December 2018<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
            agree that smaller subteams are better for getting the work
            done efficiently.  That being said, my one concern is what
            we witnessed the last go around with subteam recommendations
            and work product.  The work was done and then others
            attacked the work saying it was not representative of the
            working group, should be given little to no weight and
            should be treated the same as any proposal or comment made
            by anyone in the working group at the 11<sup>th</sup> hour. 
            If we are going to have subteams, then we should have some
            up front guidance as to how the work will be treated and the
            rules of the game.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #E1E1E1
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
                GNSO-RPM-WG <a class="moz-txt-link-rfc2396E" href="mailto:gnso-rpm-wg-bounces@icann.org"><gnso-rpm-wg-bounces@icann.org></a>
                <b>On Behalf Of </b>Jason Schaeffer<br>
                <b>Sent:</b> Thursday, December 6, 2018 10:51 AM<br>
                <b>To:</b> Michael Karanicolas
                <a class="moz-txt-link-rfc2396E" href="mailto:mkaranicolas@gmail.com"><mkaranicolas@gmail.com></a>; Julie Hedlund
                <a class="moz-txt-link-rfc2396E" href="mailto:julie.hedlund@icann.org"><julie.hedlund@icann.org></a><br>
                <b>Cc:</b> gnso-rpm-wg <a class="moz-txt-link-rfc2396E" href="mailto:gnso-rpm-wg@icann.org"><gnso-rpm-wg@icann.org></a><br>
                <b>Subject:</b> Re: [GNSO-RPM-WG] Actions & Notes:
                RPM PDP WG Meeting 05 December 2018<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi
            All,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
            agree.  I don’t believe that we concluded yesterday’s call
            with a decision to run sub teams at different times.    Many
            good points were raised regarding the value of using sub
            teams.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Per
            the proposed schedule, we need to move quickly and
            effectively – there’s much ground to cover.   Thus, having
            those dedicated to doing extra work and participating in
            smaller groups that are delegated with a task is critical to
            this WG’s success.  
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Being
            a sub-team chair I can say with certainty that the ability
            of the sub team to work efficiently and effectively depends,
            in part, on the size of the sub-team.    It’s not intended
            to be a replication of the WG.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Running
            parallel sub teams is also much more efficient.    I’m also
            concerned that 13:00 UTC is problematic for PST and others.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Jason<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
            GNSO-RPM-WG [<a href="mailto:gnso-rpm-wg-bounces@icann.org"
              moz-do-not-send="true">mailto:gnso-rpm-wg-bounces@icann.org</a>]
            <b>On Behalf Of </b>Michael Karanicolas<br>
            <b>Sent:</b> Wednesday, December 05, 2018 6:04 PM<br>
            <b>To:</b> Julie Hedlund<br>
            <b>Cc:</b> gnso-rpm-wg<br>
            <b>Subject:</b> Re: [GNSO-RPM-WG] Actions & Notes: RPM
            PDP WG Meeting 05 December 2018<o:p></o:p></span></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <div>
          <p class="MsoNormal">Hi all,<o:p></o:p></p>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">Thanks as always to staff for writing
              this up. <o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">Just with regard to the subgroups and
              timing, I didn't chime in on the call because I don't feel
              strongly either way, but thinking about it in retrospect,
              and about my experiences on the URS, I wonder if the
              smaller size of the subgroups is a feature of the system,
              since it makes discussions less unwieldy to have 10 or 15
              participants, rather than 30 or 40. <o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">Obviously, it's problematic to take any
              measures to restrict participation, but having the calls
              occur at the same time is sort of a softer method of
              achieving a smaller group for discussions, particularly if
              people who are interested are free to float back and forth
              between the two. <o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">Just a thought, since I don't know that
              that angle was raised - that the inability to participate
              in both groups at the same time as being a feature of the
              system.<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">Best,<o:p></o:p></p>
          </div>
          <div>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
          <div>
            <p class="MsoNormal">Michael<o:p></o:p></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <div>
          <div>
            <p class="MsoNormal">On Wed, Dec 5, 2018 at 4:48 PM Julie
              Hedlund <<a href="mailto:julie.hedlund@icann.org"
                moz-do-not-send="true">julie.hedlund@icann.org</a>>
              wrote:<o:p></o:p></p>
          </div>
          <blockquote style="border:none;border-left:solid #CCCCCC
            1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
            <div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                    style="color:black">Dear All,</span><o:p></o:p></p>
                <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px"><span
                    style="color:black"> </span><o:p></o:p></p>
                <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px"><span
                    style="color:black">Please see below the action
                    items and notes captured by staff from the<span
                      class="m8319100771079976775apple-converted-space"> </span></span>RPM
                  PDP Working Group<span style="color:black"> call held
                    on</span> 05 December 2018<span style="color:black">
                    (</span>17:00-18:30<span style="color:black"> UTC). 
                    Staff have posted to the wiki space the action items
                    and notes.  <b><i>Please note that these
                      </i></b></span><b><i>are<span style="color:black">
                        high-level notes and are not meant as a
                        substitute for the recording</span>, chat room,
                      or transcript</i></b><i><span style="color:black">.</span></i><span
                    style="color:black"> The recording, AC chat,</span>
                  transcript<span style="color:black"> and attendance
                    records are posted on the wiki<span
                      class="m8319100771079976775apple-converted-space"> </span>at</span>:
                  <a
href="https://community.icann.org/display/RARPMRIAGPWG/2018-12-05+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG"
                    target="_blank" moz-do-not-send="true">
https://community.icann.org/display/RARPMRIAGPWG/2018-12-05+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG</a>.
                  <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">See
                  also the attached referenced documents.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
                    style="color:black">   </span><o:p></o:p></p>
                <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px"><span
                    style="color:black">Best Regards,</span><o:p></o:p></p>
                <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px">Julie<o:p></o:p></p>
                <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;font-variant-caps:normal;text-align:start;word-spacing:0px">Julie
                  Hedlund, Policy Director<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif""> </span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif"">==</span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif""> </span><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>NOTES
                    & ACTION ITEMS</b><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>Actions:</b><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <ol start="1" type="1">
                  <li class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
                    level1 lfo1">
                    Staff to send out a Call for Volunteers for the
                    Sunrise and Claims Sub Teams<o:p></o:p></li>
                  <li class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
                    level1 lfo1">
                    Staff to schedule Sub Team calls<o:p></o:p></li>
                </ol>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>Notes:</b><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">1. 
                  Review Agenda/Statements of Interest Updates: None.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">2. 
                  Discuss Proposed Sub Team Approach, Scope of Work, and
                  Call for Volunteers -- see attached documents:<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">1)
                  Draft RPM Timeline August 2018-September 2019 –
                  updated 03 December  2018 by ICANN staff (Phase 1):<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Discussion:<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Concerns: 1) Simultaneous meetings -- prevents
                  participation in both Sub Teams.  Could schedule on
                  alternate dates or could use early time slot. 2)
                  opening individual proposals on the 2nd and close on
                  23 January -- complete analysis of the data first?<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  There will be updates to the full WG, which would help
                  the individuals to prepare their proposals.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Concerned that if we can only participate in one sub
                  team could that encourage those who aren't
                  participating to make individual proposals.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Support sub teams meeting in parallel, but not at the
                  same time.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  The Sub Teams could meet at 1300 and 1700 UTC on
                  Wednesdays, if there is enough participation.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Could also use a Friday time and report back on
                  Monday.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Seems pointless to start on Phase 2 in the middle;
                  could we take a break?  It may be overcome by events.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  UDRP discussion could be organizational.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Seem to be deviating from the URS in that the sub
                  teams can go through the individual proposals. 
                  Concerns about whether sub teams can block individual
                  proposals.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Quick note on Sub-teams -- the idea is to: (1) break
                  the work into tracks that can run concurrently so as
                  to move forward more quickly, and (2) to apply
                  expertise to specific topics.  This shouldn't preclude
                  people from being on multiple teams and, with weekly
                  reporting to the group, should give sub-teams the
                  authority to make recommendations.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  We had already considered a lot of TMCH issues before
                  moving into URS, so we are asking people to get their
                  proposals on the table early, not that they couldn't
                  wait.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Can we move the submission period for the individual
                  proposals to be later?  Per staff the timing of the
                  submission of the individual proposals can be later.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  We can also allocate some time in the full WG when the
                  sub teams report back and have the individual present
                  the proposal and sub team chair.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  If the individual proposals wait until after the sub
                  teams have presented their results then it might add
                  time to the timeline -- although this approach does
                  not have to be decided at this point.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Have pros and cons presentations from the sub teams.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">2)
                  Status of TMCH and Related RPM Discussions<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">3)
                  Table of Final Agreed Sunrise Charter Questions and
                  Data Collected<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">4)
                  Table of Final Agreed Trademark Claims Charter
                  Questions and Data Collected<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Add page numbers (although note that the PDF is for
                  viewing only; the working document will be Google Doc
                  or Google Sheets).<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Does the data include the outreach that the PDP WG did
                  to all the SOs/ACs -- that was done in late 2016? 
                  Answer: We received one or two responses, which were
                  not data specific.  We do have them on the record and
                  when the sub teams develop recommendations they will
                  be reminded of all relevant input.  Can add as a
                  placeholder at the end of the document.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  On articles and blogs -- will the WG be collecting the
                  data?  Staff began the exercise, but since the WG was
                  considering the need for data collection, which
                  because the surveys were very extensive, it may be
                  that the survey data may address those requests.  We
                  were hoping to get further guidance since it is a lot
                  of work and we are not sure how much it is useful. 
                  <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">5)
                  TMCH Sunrise and Trademark Claims Survey Results Tool<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Add the link to the Google spreadsheet in the table.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">--
                  Staff can assist Sub Teams with questions.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
              </div>
            </div>
            <p class="MsoNormal">_______________________________________________<br>
              GNSO-RPM-WG mailing list<br>
              <a href="mailto:GNSO-RPM-WG@icann.org" target="_blank"
                moz-do-not-send="true">GNSO-RPM-WG@icann.org</a><br>
              <a
                href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg"
                target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><o:p></o:p></p>
          </blockquote>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <div class="MsoNormal" style="text-align:center" align="center">
          <hr width="100%" size="2" align="center">
        </div>
        <p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:7.5pt;font-family:"Arial","sans-serif";color:black"><br>
            Confidentiality Notice:<br>
            This communication constitutes an electronic communication
            within the meaning of the Electronic Communications Privacy
            Act, 18 U.S.C. Section 2510, and its disclosure is strictly
            limited to the recipient intended by the sender of this
            message. This transmission, and any attachments, may contain
            confidential attorney-client privileged information and
            attorney work product. If you are not the intended
            recipient, any disclosure, copying, distribution or use of
            any of the information contained in or attached to this
            transmission is STRICTLY PROHIBITED. Please contact us
            immediately by return e-mail or at 404 815 6500, and destroy
            the original transmission and its attachments without
            reading or saving in any manner.</span><o:p></o:p></p>
        <div class="MsoNormal" style="text-align:center" align="center">
          <hr width="100%" size="2" align="center">
        </div>
        <p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Arial","sans-serif";color:black"><br>
            ***DISCLAIMER*** Per Treasury Department Circular 230: Any
            U.S. federal tax advice contained in this communication
            (including any attachments) is not intended or written to be
            used, and cannot be used, for the purpose of (i) avoiding
            penalties under the Internal Revenue Code or (ii) promoting,
            marketing or recommending to another party any transaction
            or matter addressed herein.</span><o:p></o:p></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
GNSO-RPM-WG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GNSO-RPM-WG@icann.org">GNSO-RPM-WG@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a></pre>
    </blockquote>
  </body>
</html>