<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Great questions!! <br>
    </p>
    <div class="moz-cite-prefix">On 10/23/2024 11:10 AM, Pedro de
      Perdigão Lana wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAGSP6RRN8Jp81uYyy0Sk04F-KadRzySv5mSU1XyNbLFhPNoYAw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="auto">Hi Julf, Benjamin,</div>
        <div dir="auto"><br>
        </div>
        <div>[This message was kept in draft, forgot to send it -_-]<br>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">I have one related to the RDRS.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">ICANN logic is heavily marked by, for lack of a
          better concept, a North American perspective on how to do
          business and how procedures (f. ex., legal frameworks) should
          work. However, the RDRS is a result of, if we could say that,
          a more European-ish way to see human rights and to protect
          them. When we talk about the transparency and accountability
          of the RDRS, those values seem to be more heavily aligned with
          a human rights-centered view of how the system should work.
          However, we have seen lots of times a preference to protect
          ICANN’s or CPH’s trade secrets or confidentiality. Does the
          board think that ICANN should turn itself to a more
          HR-centered approach when the org and the community plan the
          next steps of the RDRS? What does that mean regarding the
          transparency of the system?</div>
        <div dir="auto"><br>
        </div>
        <div>Cordially,<br clear="all">
        </div>
        <div dir="auto"><br clear="all">
          <div dir="auto">
            <div dir="ltr" class="gmail_signature"
              data-smartmail="gmail_signature">
              <div dir="ltr"><span
style="font-family:garamond,"times new roman",serif"><font
                    size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><b
style="font-family:garamond,"times new roman",serif">Pedro de
                      Perdigão Lana</b><br>
                  </font></span>
                <div><span
style="font-family:garamond,"times new roman",serif"><font
                      size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><a
                        href="https://www.nic.br/"
style="font-family:garamond,"times new roman",serif"
                        target="_blank" moz-do-not-send="true">Advogado
                        - OAB/PR 90.600</a>,  </font></span><span
style="font-family:garamond,"times new roman",serif"><font
                      size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><span
style="font-family:garamond,"times new roman",serif"><font
                          size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><span
style="font-family:garamond,"times new roman",serif"><font
                              size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)">Pesquisador
                              (<a href="https://www.gedai.com.br/"
style="font-family:garamond,"times new roman",serif"
                                target="_blank" moz-do-not-send="true">GEDAI/UFPR</a>)</font></span></font></span></font></span></div>
                <div><span
style="font-family:garamond,"times new roman",serif"><font
                      size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)">Doutorando
                      em Direito (UFPR), Mestre em Direito Empresarial
                      (UCoimbra), </font></span></div>
                <div><span
style="font-family:garamond,"times new roman",serif"><font
                      size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)">Coordenação/Diretoria/EC
                      @ </font></span><span
style="font-family:garamond,"times new roman",serif"><font
                      size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><span
style="font-family:garamond,"times new roman",serif"><a
                          href="https://isoc.org.br/"
style="font-family:garamond,"times new roman",serif"
                          target="_blank" moz-do-not-send="true">ISOC BR</a></span></font><font
                      size="1"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><font
                        size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)">,</font></font></span><span
style="font-family:garamond,"times new roman",serif"><font
                      size="1"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><font
                        size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)">
                      </font></font><font size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><a
                        href="https://www.ncuc.org"
style="font-family:garamond,"times new roman",serif"
                        target="_blank" moz-do-not-send="true">NCUC</a>
                      & <a
href="https://community.icann.org/display/gnsononcomstake/Home"
style="font-family:garamond,"times new roman",serif"
                        target="_blank" moz-do-not-send="true">NCSG </a>(ICANN),
                      <a href="https://youthlacigf.lat/"
style="font-family:garamond,"times new roman",serif"
                        target="_blank" moz-do-not-send="true">YouthLACIGF</a>,</font></span><span
style="font-family:garamond,"times new roman",serif"><font
                      size="1"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><font
                        size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)">
                        <a href="https://ioda.org.br/"
style="font-family:garamond,"times new roman",serif"
                          target="_blank" moz-do-not-send="true">IODA</a>
                        e </font></font></span><span
style="font-family:garamond,"times new roman",serif"><font
                      size="1"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><font
                        size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)"><a
                          href="https://br.creativecommons.net/"
style="font-family:garamond,"times new roman",serif"
                          target="_blank" moz-do-not-send="true">CC
                          Brasil</a></font></font></span><span
style="font-family:garamond,"times new roman",serif"><font
                      size="2"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)">.</font></span></div>
                <div><span
style="font-family:garamond,"times new roman",serif"></span></div>
                <span
style="font-family:garamond,"times new roman",serif"><font
                    size="1"
style="font-family:garamond,"times new roman",serif;color:rgb(0,0,0)">Essa
                    mensagem é restrita ao remetente e destinatário(s).
                    Se recebida por engano, favor responder informando o
                    erro.</font></span><br>
              </div>
            </div>
          </div>
        </div>
      </div>
      <div><br>
      </div>
      <div><br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">Em seg., 14 de out. de 2024
            às 10:47, Johan Helsingius <<a
href="mailto:00001963cc94b85a-dmarc-request@listserv.syr.edu"
              target="_blank" moz-do-not-send="true"
              class="moz-txt-link-freetext">00001963cc94b85a-dmarc-request@listserv.syr.edu</a>>
            escreveu:<br>
          </div>
          <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Any
            topics you think we should bring up in our meeting with the
            Board?<br>
            <br>
            "We kindly request that you send any questions you would
            like the Board<br>
              to address during our face-to-face meetings to Board
            Operations (board-<br>
              <a href="mailto:ops-team@icann.org" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">ops-team@icann.org</a>).
            Given the limited time for these meetings, please<br>
              prioritize your questions in order of importance. We would
            appreciate<br>
              receiving your questions no later than Wednesday 30
            October 2024."<br>
            <br>
                    Julf<br>
            <br>
            <br>
            -------- Forwarded Message --------<br>
            Subject:        ICANN81 Stakeholders/Board sessions<br>
            Date:   Tue, 8 Oct 2024 06:15:40 +0000<br>
            From:   Vinciane Koenigsfeld <<a
              href="mailto:vinciane.koenigsfeld@icann.org"
              target="_blank" moz-do-not-send="true"
              class="moz-txt-link-freetext">vinciane.koenigsfeld@icann.org</a>><br>
            To:     <a href="mailto:julf@julf.com" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">julf@julf.com</a>
            <<a href="mailto:julf@julf.com" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">julf@julf.com</a>>,
            <a href="mailto:benakin@gmail.com" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">benakin@gmail.com</a>
            <br>
            <<a href="mailto:benakin@gmail.com" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">benakin@gmail.com</a>>,
            <a href="mailto:jumaropi@yahoo.com" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">jumaropi@yahoo.com</a>
            <<a href="mailto:jumaropi@yahoo.com" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">jumaropi@yahoo.com</a>>,
            <br>
            <a href="mailto:mcknight.glenn@gmail.com" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">mcknight.glenn@gmail.com</a>
            <<a href="mailto:mcknight.glenn@gmail.com"
              target="_blank" moz-do-not-send="true"
              class="moz-txt-link-freetext">mcknight.glenn@gmail.com</a>><br>
            CC:     Carlos Reyes <<a
              href="mailto:carlos.reyes@icann.org" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">carlos.reyes@icann.org</a>>,
            Michelle Bright <br>
            <<a href="mailto:michelle.bright@icann.org"
              target="_blank" moz-do-not-send="true"
              class="moz-txt-link-freetext">michelle.bright@icann.org</a>>,
            Board Ops Team <<a href="mailto:board-ops-team@icann.org"
              target="_blank" moz-do-not-send="true"
              class="moz-txt-link-freetext">board-ops-team@icann.org</a>>,
            <br>
            Mary Wong <<a href="mailto:mary.wong@icann.org"
              target="_blank" moz-do-not-send="true"
              class="moz-txt-link-freetext">mary.wong@icann.org</a>><br>
            <br>
            <br>
            <br>
            /Sent on behalf of Tripti Sinha, Chair, ICANN Board of
            Directors///<br>
            <br>
            DearNon/c//ommercial Stakeholder Group///Leaders,<br>
            <br>
            Our Annual General Meeting (9-14 November) is approaching
            quickly, and <br>
            the Board and I are looking forward to meeting with all of
            you in Istanbul.<br>
            <br>
            It will be our final meeting of 2024, a year marked by both
            challenges <br>
            and progress. Notably, we celebrated the selection of our
            new CEO, <br>
            Kurtis Lindqvist, who will soon officially take on the role.<br>
            <br>
            As we finalize our new five-year Strategic Plan and continue
            <br>
            collaborating on key projects critical to ICANN’s
            future—including the <br>
            launch of the Next Round of new gTLDs— we remain committed
            to <br>
            strengthening our partnership. In keeping with our practice
            before <br>
            ICANN79, the Board plans to hold an open engagement session
            during Prep <br>
            Week of ICANN81, allowing interested community members to
            engage <br>
            directly with the Board on specific topics. *This session
            will be held <br>
            on 28 October at 15:00 UTC.*<br>
            <br>
            The 60-minute session will feature two breakout rooms, each
            hosted by <br>
            different Board members and focused on distinct topics.
            After a brief <br>
            welcome plenary, participants will be invited to join one of
            the two <br>
            breakout rooms for a 45-minute discussion with the Board
            hosts. <br>
            Attendees will have the flexibility to move between the
            breakout rooms. <br>
            The session will conclude with a summary from each Board
            host on the <br>
            discussions held in their respective breakout rooms.<br>
            <br>
            **<br>
            <br>
            *Topic 1:Future of the new gTLD Program: Applications in
            rounds or <br>
            continuously accepting applications (first come, first
            serve)?*<br>
            <br>
               * Led by Becky Burr and Alan Barrett<br>
               * Format of the engagement: discussion and soliciting
            input<br>
               * Description: To date, the new gTLD Program has operated
            in rounds,<br>
                 allowing applicants to submit their applications within
            specific<br>
                 time windows. The last round took place in 2012, and
            the next one is<br>
                 expected to open in 2026. Due to concerns raised by the
            Board, the<br>
                 GNSO Council has expressed interest<br>
            <br>
            <<a
href="https://gnso.icann.org/sites/default/files/policy/2023/correspondence/ducos-to-icann-board-et-al-05sep23-en.pdf"
              rel="noreferrer" target="_blank" moz-do-not-send="true"
              class="moz-txt-link-freetext">https://gnso.icann.org/sites/default/files/policy/2023/correspondence/ducos-to-icann-board-et-al-05sep23-en.pdf</a>> in<br>
                 collaborating with the ICANN Board on the long-term
            evolution of the<br>
                 program, potentially moving away from the current
            round-based<br>
                 approach. Several issues have been identified with the
            round-based<br>
                 approach, including:<br>
            <br>
            1. Dealing with contention sets, which have proven to be one
            of the most <br>
            complex and litigious part of the program.<br>
            <br>
            2. The costs and challenges of repeatedly switching the
            program on and off.<br>
            <br>
            3. The sense of scarcity and rush to apply created by
            limited <br>
            application windows.<br>
            <br>
            This session will explore what a future New gTLD Program
            might look like <br>
            if applications were submitted continuously, similar to
            ICANN’s approach <br>
            for other programs like registrar accreditation. Key
            questions to <br>
            consider include:<br>
            <br>
            · What advantages, if any, are there to maintaining the
            round-based system?<br>
            <br>
            · What challenges would arise from a continuously open New
            gTLD Program?<br>
            <br>
            · Are there alternative models that could address the
            identified issues?<br>
            <br>
            · Given current priorities, what is a realistic timeline for
            developing <br>
            policies on this issue that would allow a different<br>
            <br>
            approach?<br>
            <br>
            *Topic 2: RDRS Community Feedback*<br>
            <br>
               * Led by Maarten Botterman and Wes Hardaker<br>
               * Format of the engagement: discussion and soliciting
            input<br>
               * Description: The<br>
                 Board seeks to understand the community’s perception
            of RDRS<br>
                 after nearly a year of operations, particularly whether
            the<br>
                 community agrees that the service could be a suitable
            permanent<br>
                 solution for access to registration data. This feedback
            will help<br>
                 guide the Board’s next steps in discussions with the
            GNSO Council<br>
                 regarding the future of the EPDP Phase 2 policy
            recommendations for<br>
                 a System for a Standardized/Access Disclosure<br>
            <br>
            The Board looks forward to this engagement opportunity and
            encourages <br>
            your active participation.<br>
            <br>
            Please note that ICANN Staff will support this engagement
            session and <br>
            take notes. However, there will be technical limitations in
            the breakout <br>
            rooms, including the absence of interpretation and
            transcription services.<br>
            <br>
            As always, we will listen to your specific needs during our
            bilateral <br>
            sessions. In keeping with our established practice, we will
            also ask a <br>
            question to your Group ahead of our joint session in
            Istanbul.<br>
            <br>
            *- The Board has been continuing work on a Global Public
            Interest <br>
            Framework in relation to ICANN policy making, and has
            recently finalised <br>
            a draft GPI Framework Checklist. The Board is eager to hear
            feedback <br>
            from the Council on this checklist, including whether the
            Council feels <br>
            this will be a useful policy development tool and any
            thoughts on how it <br>
            could be further developed.<br>
            <br>
            *<br>
            <br>
            We look forward to hearing your thoughts on this soon.<br>
            <br>
            We kindly request that you send any questions you would like
            the Board <br>
            to address during our face-to-face meetings to Board
            Operations <br>
            (<a href="mailto:board-ops-team@icann.org" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">board-ops-team@icann.org</a>
            <mailto:<a href="mailto:board-ops-team@icann.org"
              target="_blank" moz-do-not-send="true"
              class="moz-txt-link-freetext">board-ops-team@icann.org</a>>).
            Given the <br>
            limited time for these meetings, please prioritize your
            questions in <br>
            order of importance. We would appreciate receiving your
            questions no <br>
            later than *Wednesday 30 October 2024.*<br>
            <br>
            Looking forward to our discussions during Prep Week and
            ICANN81!<br>
            <br>
            Best regards,<br>
            <br>
            Tripti Sinha<br>
            <br>
            Chair, ICANN Board of Directors<br>
          </blockquote>
        </div>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre wrap="" class="moz-quote-pre">_______________________________________________
Ncuc-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ncuc-discuss@lists.ncuc.org">Ncuc-discuss@lists.ncuc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a>
</pre>
    </blockquote>
  </body>
</html>