<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi Rafik, would it be possible to add a link to the full paper? 
      I see that the CSG has commented broadly, and I'm happy to do the
      same (and hope others will as well!).</p>
    <p>Tx, Kathu<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 7/2/2018 6:26 AM, Rafik Dammak
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAH5sThmTYB688W4i45UZWVXUcTbqLi6je4wHkhaLyH-bFcN2wA@mail.gmail.com">
      <div dir="ltr">Hi,
        <div><br>
        </div>
        <div>this is the input from BC on PDP 3.0 report. there is an
          extension for SG/C to send their comments on the report.</div>
        <div>we have a google doc to populate with an NCSG input <a
href="https://docs.google.com/document/d/13iQjVPy_yqfMu0jT3CrNu0WfHfyXLOWSMGaGb3PnnnM/edit"
            moz-do-not-send="true">https://docs.google.com/document/d/13iQjVPy_yqfMu0jT3CrNu0WfHfyXLOWSMGaGb3PnnnM/edit</a>.</div>
        <div><br>
        </div>
        <div>Best,</div>
        <div><br>
        </div>
        <div>Rafik<br>
          <br>
          <br>
          <div class="gmail_quote">
            <div dir="ltr">---------- Forwarded message ---------<br>
              From: <strong class="gmail_sendername" dir="auto">Marie
                Pattullo</strong> <span dir="ltr"><<a
                  href="mailto:marie.pattullo@aim.be" target="_blank"
                  moz-do-not-send="true">marie.pattullo@aim.be</a>></span><br>
              Date: lun. 2 juil. 2018 à 19:13<br>
              Subject: [council] GNSO PDP 3.0 discussion paper<br>
              To: GNSO Council List <<a
                href="mailto:council@gnso.icann.org" target="_blank"
                moz-do-not-send="true">council@gnso.icann.org</a>><br>
            </div>
            <br>
            <br>
            <div lang="EN-GB">
              <div
                class="gmail-m_-5804707641590519102m_442394736407460707WordSection1">
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)"> </span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)">Dear
                    all,</span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)">Trust
                    you had a good journey home!</span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)">As
                    requested during our meetings last week, please see
                    below the input that the BC provided on PDP 3.0.
                    We’re of course more than happy to discuss further.</span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)">Kind
                    regards,</span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)">Marie</span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)"> </span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)"> </span></p>
                <div>
                  <div
style="border-right:none;border-bottom:none;border-left:none;border-top:1pt
                    solid rgb(225,225,225);padding:3pt 0cm 0cm">
                    <p class="MsoNormal"><b><span style="font-size:11pt"
                          lang="EN-US">From:</span></b><span
                        style="font-size:11pt" lang="EN-US"> Marie
                        Pattullo
                        <br>
                        <b>Sent:</b> Friday, June 8, 2018 4:42 PM<br>
                        <b>To:</b> 'Marika Konings' <<a
                          href="mailto:marika.konings@icann.org"
                          target="_blank" moz-do-not-send="true">marika.konings@icann.org</a>>;
                        Heather Forrest <<a
                          href="mailto:haforrestesq@gmail.com"
                          target="_blank" moz-do-not-send="true">haforrestesq@gmail.com</a>>;
                        Austin, Donna <<a
                          href="mailto:Donna.Austin@team.neustar"
                          target="_blank" moz-do-not-send="true">Donna.Austin@team.neustar</a>>;
                        'Rafik Dammak' <<a
                          href="mailto:rafik.dammak@gmail.com"
                          target="_blank" moz-do-not-send="true">rafik.dammak@gmail.com</a>><br>
                        <b>Cc:</b> <a href="mailto:bc-excomm@icann.org"
                          target="_blank" moz-do-not-send="true">bc-excomm@icann.org</a><br>
                        <b>Subject:</b> RE: GNSO PDP 3.0 discussion
                        paper</span></p>
                  </div>
                </div>
                <p class="MsoNormal"> </p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)">All,</span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)">Many
                    thanks for this. As requested, input from the BC is
                    below.</span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)">Kind
                    regards</span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)">Marie</span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)"> </span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)"> </span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)">The BC
                    welcomes the discussion of how to improve the GNSO
                    Policy Development Process (PDP). Ensuring an
                    efficient and effective way to gather, synthesise
                    and advance community-based policies is a vital part
                    of ICANN’s DNA.</span><span lang="EN-US"></span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)"> </span><span
                    lang="EN-US"></span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)">As a
                    starting point, not only has the current average
                    timeline for PDPs increased, so has the amount of
                    working groups, reviews and policy dossiers – not
                    least the unprecedented EPDP/Temporary Specification
                    work. A balance must be found between allowing
                    enough time and community input on the one hand and
                    an efficient and timely process on the other; we
                    thank the Council leadership and staff for setting
                    out the challenges in a concise and realistic way.
                    Taking the potential incremental improvements in
                    order:</span><span lang="EN-US"></span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)"> </span><span
                    lang="EN-US"></span></p>
                <p class="MsoNormal"><b><i><span
                        style="font-size:11pt;color:rgb(31,73,125)">Working
                        Group Dynamics
                      </span></i></b><span lang="EN-US"></span></p>
                <ul style="margin-top:0cm" type="disc">
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Terms of participation
                        for WG members</span></i><span
                      style="font-size:11pt">: while a “Commitment of
                      Participation” template may be worthwhile, in
                      practice this is unlikely to have a practical
                      effect on participation. We already have standards
                      of behaviour but experience shows that this does
                      not stop bad faith or even the wilfully
                      unpleasant, and at a lesser level one person’s
                      joke is another’s affront. This would have to be
                      policed carefully.</span><span lang="EN-US"></span></li>
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Consider alternatives to
                        open WG model</span></i><span
                      style="font-size:11pt">: designation by
                      SO/AC/SG/Cs should help to ensure more objectivity
                      and expertise, but we would add that the designee
                      should also act as the conduit for their
                      designator’s views and not in their personal
                      capacity. Individuals must be allowed to join as
                      either participants or observers to preserve the
                      multistakeholder model; would it however be
                      possible to consider “weighted voting” in
                      contentious matters (so more “weight” for
                      designees)? For example, could the Chair call a
                      vote on a discussion point when it seems that
                      deadlock has been reached based on ideology rather
                      than reason and community benefit?</span><span
                      lang="EN-US"></span></li>
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Limitations to joining of
                        new members after a certain time</span></i><span
                      style="font-size:11pt">: if this is to happen, new
                      observers must still be allowed to join and
                      newsletters issued regularly to ensure
                      transparency. The decision to widen/restrict the
                      membership should not fall on the PDP leadership
                      alone, but on Council as a whole to prevent
                      unwarranted pressure/capture of the Chairs.
                    </span><span lang="EN-US"></span></li>
                </ul>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)"> </span><span
                    lang="EN-US"></span></p>
                <p class="MsoNormal"><b><i><span
                        style="font-size:11pt;color:rgb(31,73,125)">WG
                        Leadership</span></i></b><span
                    style="font-size:11pt;color:rgb(31,73,125)">
                  </span><span lang="EN-US"></span></p>
                <ul style="margin-top:0cm" type="disc">
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Capture vs. Consensus
                        Playbook</span></i><span style="font-size:11pt">:
                      any practical tools and support to ensure
                      effective and efficient leadership should be seen
                      as a positive. Experienced Chairs/leadership would
                      be the most obvious drafters to share hands-on
                      experience and solutions.</span><span lang="EN-US"></span></li>
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Active role for and clear
                        description of Council liaison to PDP WGs</span></i><span
                      style="font-size:11pt">: support.</span><span
                      lang="EN-US"></span></li>
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Document expectations for
                        WG leaders that outlines role &
                        responsibilities as well as minimum skills /
                        expertise required</span></i><span
                      style="font-size:11pt">: support.</span><span
                      lang="EN-US"></span></li>
                </ul>
                <p class="MsoNormal"><i><span
                      style="font-size:11pt;color:rgb(31,73,125)"> </span></i><span
                    lang="EN-US"></span></p>
                <p class="MsoNormal"><b><i><span
                        style="font-size:11pt;color:rgb(31,73,125)">Complexity
                        of Subject Matter
                      </span></i></b><span lang="EN-US"></span></p>
                <ul style="margin-top:0cm" type="disc">
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Creation of Cooperative
                        Teams</span></i><span style="font-size:11pt">:
                      while we understand the good faith reasoning, this
                      goes against the idea of the “Commitment of
                      Participation” and could develop into a shortcut
                      for those who do not/cannot engage who then rely
                      on these Teams to do extra work/outreach to
                      compensate for their lack of engagement. It would
                      also lead to further complexity by adding another
                      structural element that could cause confusion
                      about who really is the shaping the PDP – the
                      drafting team, the subgroup, the Chair,
                      Cooperative Team..? It could also be vulnerable to
                      claims that the Teams were misdirecting the
                      members/ misrepresenting the discussions.</span><span
                      style="font-size:11pt;color:windowtext">
                    </span><span lang="EN-US"></span></li>
                </ul>
                <p
                  class="gmail-m_-5804707641590519102m_442394736407460707MsoListParagraph"
                  style="margin-right:36pt">
                  <span style="font-family:Symbol;color:rgb(31,73,125)"
                    lang="EN-US"><span>·<span style="font:7pt
                        "Times New Roman"">        
                      </span></span></span><i><span
                      style="font-size:11pt;color:rgb(31,73,125)">PDP
                      Plenary or Model PDP</span></i><span
                    style="font-size:11pt;color:rgb(31,73,125)">: full
                    support.</span><span style="color:rgb(31,73,125)"
                    lang="EN-US"></span></p>
                <p
                  class="gmail-m_-5804707641590519102m_442394736407460707MsoListParagraph"><span
                    style="font-size:11pt;color:rgb(31,73,125)"> </span><span
                    lang="EN-US"></span></p>
                <p class="MsoNormal"><b><i><span
                        style="font-size:11pt;color:rgb(31,73,125)">Consensus
                        Building</span></i></b><span
                    style="font-size:11pt;color:rgb(31,73,125)"></span></p>
                <ul style="margin-top:0cm" type="disc">
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Provide further guidance
                        for sections 3.6 (Standard Methodology for
                        decision making)</span></i><span
                      style="font-size:11pt">: general support but a
                      note of caution:  “Consensus” means different
                      things to different organisations and at the
                      beginning of a PDP it would be helpful to remind
                      everyone about what “consensus” will mean in the
                      PDP process. However there is value in considering
                      consensus-building lessons and approaches used by
                      other organisations.</span></li>
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Document positions at the
                        outset</span></i><span style="font-size:11pt">:
                      possible, but would this not extend the opening
                      phases of the PDP before substantive work could
                      start? And whose positions – those of members, or
                      aggregate views? There will also by default be
                      sub-positions of positions. We are not convinced
                      that this would be of benefit.</span><span
                      lang="EN-US"></span></li>
                </ul>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)"> </span><span
                    lang="EN-US"></span></p>
                <p class="MsoNormal"><b><i><span
                        style="font-size:11pt;color:rgb(31,73,125)">Role
                        of Council as Manager of the PDP</span></i></b><span
                    lang="EN-US"></span></p>
                <ul style="margin-top:0cm" type="disc">
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Enforce deadlines and
                        ensure bite size pieces</span></i><span
                      style="font-size:11pt">: full support.</span><span
                      lang="EN-US"></span></li>
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Notification to Council
                        of changes in work plan</span></i><span
                      style="font-size:11pt">: full support.</span><span
                      lang="EN-US"></span></li>
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Review of Chair(s</span></i><span
                      style="font-size:11pt">): this leads to a further
                      question – do we need a policy on the appointment
                      of Chairs in the first place? While we support the
                      idea of a “process... that allows a WG to
                      challenge and/or replace its leadership team” this
                      should be carefully crafted. The 12-month
                      reappointment seems sensible.</span><span
                      lang="EN-US"></span></li>
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Make better use of
                        existing flexibility in PDP to allow for data
                        gathering, chartering and termination when it is
                        clear that no consensus can be achieved</span></i><span
                      style="font-size:11pt">: support.</span><span
                      lang="EN-US"></span></li>
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Independent conflict
                        resolution</span></i><span
                      style="font-size:11pt">: We are concerned that an
                      independent conflict resolution process has the
                      potential of becoming the default way to resolve
                      seemingly intractable WG disagreements rather than
                      forcing WG members to do the hard work of
                      consensus-building and employing the toolkit of
                      possible responses mentioned under WG Leadership.
                      After two years under the revised PDP process, we
                      might then reconsider the desirability/need for
                      recourse to independent conflict resolution.
                      Further - who would do this? If external – cost
                      implications? Could it fall under the remit of
                      (e.g.) the Standing Selection Committee? Whoever
                      it is, this should be known to all WGs from the
                      outset.</span></li>
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Criteria for PDP WG
                        Updates</span></i><span style="font-size:11pt">:
                      support.</span><span lang="EN-US"></span></li>
                  <li class="MsoNormal" style="color:rgb(31,73,125)"><i><span
                        style="font-size:11pt">Resource reporting for
                        PDP WGs</span></i><span style="font-size:11pt">:
                      support.</span><span lang="EN-US"></span></li>
                </ul>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)"> </span><span
                    lang="EN-US"></span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)"
                    lang="EN-US"> </span></p>
                <p class="MsoNormal"><span
                    style="font-size:11pt;color:rgb(31,73,125)"> </span></p>
                <div>
                  <div
style="border-right:none;border-bottom:none;border-left:none;border-top:1pt
                    solid rgb(225,225,225);padding:3pt 0cm 0cm">
                    <p class="MsoNormal"><b><span style="font-size:11pt"
                          lang="EN-US">From:</span></b><span
                        style="font-size:11pt" lang="EN-US"> council
                        <<a
                          href="mailto:council-bounces@gnso.icann.org"
                          target="_blank" moz-do-not-send="true">council-bounces@gnso.icann.org</a>>
                        <b>On Behalf Of </b>Marika Konings<br>
                        <b>Sent:</b> Friday, May 11, 2018 11:24 PM<br>
                        <b>To:</b> <a
                          href="mailto:council@gnso.icann.org"
                          target="_blank" moz-do-not-send="true">council@gnso.icann.org</a><br>
                        <b>Subject:</b> [council] GNSO PDP 3.0
                        discussion paper</span></p>
                  </div>
                </div>
                <p class="MsoNormal"> </p>
                <p class="MsoNormal"><i><span style="font-size:11pt"
                      lang="EN-US">Sending on behalf of the Council
                      leadership</span></i></p>
                <p class="MsoNormal"><span style="font-size:11pt"
                    lang="EN-US"> </span></p>
                <p class="MsoNormal" style="line-height:18pt"><span
                    style="color:black" lang="EN-US">Dear colleagues,</span></p>
                <p class="MsoNormal" style="line-height:18pt"><span
                    style="color:black" lang="EN-US"> </span></p>
                <p class="MsoNormal" style="line-height:18pt"><span
                    style="color:black" lang="EN-US">Please find
                    attached for your review the GNSO PDP 3.0 discussion
                    paper. The Council leadership team has collaborated
                    with staff in bringing all discussions and
                    suggestions to date into one document for your and
                    your respective communities’ consideration. We
                    welcome input, particularly on section 4 – potential
                    incremental improvements for consideration. In
                    particular, which potential incremental improvements
                    should be prioritized, are there any missing, are
                    there additional implementation steps that should be
                    considered? After receiving feedback, we hope to
                    commence the development of an implementation plan
                    proposing the when/how/who of implementing those
                    incremental improvements agreed upon by the Council.
                    To contribute to this next step in the improvements
                    process we kindly request your feedback and/or that
                    of your community by 8 June so that the Council can
                    consider next steps during its meeting at ICANN62.
                  </span></p>
                <p class="MsoNormal"><span lang="EN-US"> </span></p>
                <p class="MsoNormal"><span lang="EN-US">Best regards,</span></p>
                <p class="MsoNormal"><span lang="EN-US"> </span></p>
                <p class="MsoNormal"><span lang="EN-US">GNSO Council
                    leadership team</span></p>
                <p class="MsoNormal"><span style="font-size:11pt"
                    lang="EN-US"> </span></p>
                <p class="MsoNormal"><b><i><span style="font-size:11pt"
                        lang="EN-US">Marika Konings</span></i></b></p>
                <p class="MsoNormal"><i><span style="font-size:11pt"
                      lang="EN-US">Vice President, Policy Development
                      Support – GNSO, Internet Corporation for Assigned
                      Names and Numbers (ICANN) </span></i></p>
                <p class="MsoNormal"><i><span style="font-size:11pt"
                      lang="EN-US">Email: <a
                        href="mailto:marika.konings@icann.org"
                        target="_blank" moz-do-not-send="true">
                        marika.konings@icann.org</a>  </span></i></p>
                <p class="MsoNormal"><i><span style="font-size:11pt"
                      lang="EN-US"> </span></i></p>
                <p class="MsoNormal"><i><span style="font-size:11pt"
                      lang="EN-US">Follow the GNSO via Twitter
                      @ICANN_GNSO</span></i></p>
                <p class="MsoNormal"><i><span style="font-size:11pt"
                      lang="EN-US">Find out more about the GNSO by
                      taking our <a
                        href="http://learn.icann.org/courses/gnso"
                        target="_blank" moz-do-not-send="true">interactive
                        courses</a> and visiting the <a
href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers"
                        target="_blank" moz-do-not-send="true">GNSO
                        Newcomer pages</a>. </span></i></p>
                <p class="MsoNormal"><span lang="EN-US"> </span></p>
              </div>
            </div>
            _______________________________________________<br>
            council mailing list<br>
            <a href="mailto:council@gnso.icann.org" target="_blank"
              moz-do-not-send="true">council@gnso.icann.org</a><br>
            <a href="https://mm.icann.org/mailman/listinfo/council"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/council</a><br>
          </div>
        </div>
      </div>
      <!--'"--><br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
    </blockquote>
    <br>
  <div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
<table style="border-top: 1px solid #D3D4DE;">
        <tr>
        <td style="width: 55px; padding-top: 13px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;" /></a></td>
                <td style="width: 470px; padding-top: 12px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Virus-free. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link" target="_blank" style="color: #4453ea;">www.avast.com</a>
                </td>
        </tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body>
</html>