<div dir="ltr">Kathy and colleagues <div><br></div><div>Good afternoon; with thanks to you and Sophie I think we are edging towards a way forward on this issue; think the two overriding objectives here are transparency and opportunity, the former in relation to everyone knowing what CG applications have been made (thus the imperative of a page / location / site where such are listed, and the latter in relation to a dedicated and distinct public consultation period; </div><div><br></div><div>best</div><div><br></div><div>Nigel</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 6 Jun 2023 at 23:57, Kathy Kleiman <kathy@dnrc.tech> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div>
    <p>Hi Sophie,</p>
    <p>I confess to being a bit confused. I don't see any language below
      that addresses the issues raised by Greg, Alan, me, and members of
      the GAC.  <br>
    </p>
    <p><font color="#b45f06"><span style="font-size:11pt;font-family:Arial,sans-serif"></span></font></p>
    Quick note that it is my understanding that GAC is under no
    obligation to follow the SubPro Working Group's recommendation that
    Early Warnings run at the same time as Reveal Day public comments,
    and GAC is currently working on the timing of its Early Warnings.
    <p>I reattach our paper listing concerns, history and goals for <i>a
        meaningful Closed Generics comment period. <br>
      </i></p>
    <p><i> </i>
    </p>
    <p>Let me re-share Greg's email:<br>
    </p>
    <p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black;background:lime">"Please
        respond if you can live with this compromise. If you cannot,
        please offer a detailed way forward.</span><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u><u></u></span></p>
    <p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <span class="gmail_default" style="font-family:verdana,sans-serif"><font color="#b45f06">This also misses the mark and does not
            provide anything close to the result being sought by a
            significant portion of the group. As such, I can't live with
            this either. What is needed is not merely the possibility of
            the hope of the potential of an extension of the initial
            "reveal day" triggered comments period.  What is needed is a
            firm commitment to a greater opportunity to comment -- in
            the form of a second comment period for Closed Generics, to
            occur after GAC Early Warnings.  </font></span></span></p>
    <div> </div>
    <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
      <div>
        <div lang="EN-US">
          <div>
            <p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><span class="gmail_default" style="font-family:verdana,sans-serif"><font color="#b45f06">The number of Closed Generics is not
                    really relevant to whether a second period is needed
                    (or even the extension of the first period) --
                    unless we have hundreds of Closed Generics, in which
                    case even more time may be needed.  The issue is not
                    primarily that commenting organizations need time to
                    sort through a plethora of applications; rather, the
                    issue is that commenting organizations will need
                    more time than is granted to consider whether and
                    how to comment on the one, two or a few Closed
                    Generic applications that will be relevant to
                    it/them, to build awareness of the relevant
                    application(s) and get buy-in from potential
                    participants in a comment, and then to develop,
                    write, circulate to what might be a substantial
                    group of co-authors, get back comments, revise,
                    recirculate, and finalize the comments.  Underlying
                    this is a belief that comments on Closed Generics
                    are more like to come from organizations,
                    associations, and groups of like-minded entities
                    based on the very nature of the Closed Generic
                    gTLD.  That is why this treatment is critical and
                    why it is sought.</font></span></span></p>
          </div>
        </div>
      </div>
    </blockquote>
    <div><br>
    </div>
    <div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#b45f06">Proposed revisions:</font></div>
    <div class="gmail_default" style="font-family:verdana,sans-serif"><span style="color:rgb(180,95,6)"></span><br>
    </div>
    <ul style="margin-bottom:0in;margin-top:0in" type="disc">
      <li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline"><font color="#b45f06"><span style="font-size:11pt;font-family:Arial,sans-serif">Applications
            for closed generics gTLDs <span class="gmail_default" style="font-family:verdana,sans-serif">will</span> be
            subject to the same Public Comment period as all other gTLD
            applications. However, given that closed generic gTLDs are
            uniquely impactful to the public interest<span class="gmail_default" style="font-family:verdana,sans-serif"> and to the
              interests of multiple entities that may identify with a
              string</span>, the group acknowledges there should be more
            time dedicated to their Public Comments. <span class="gmail_default" style="font-family:verdana,sans-serif">T</span>he Public
            Comment period will <span class="gmail_default" style="font-family:verdana,sans-serif">supplemented by an
              additional </span>60 day<span class="gmail_default" style="font-family:verdana,sans-serif"> comment period </span>solely
            for closed generic gTLD application comments<span class="gmail_default" style="font-family:verdana,sans-serif">, to commence upon
              the submission of Early Warnings by the GAC and its
              members</span>. This does not replace ICANN’s discretion
            to extend the Public Comment period for all applications,
            and the 60-day extension will apply to the full length of
            the Public Comment period (extended or otherwise). </span><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u><u></u></span></font>
        <ul style="margin-bottom:0in;margin-top:0in" type="circle">
          <li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline"><font color="#b45f06"><span style="font-size:11pt;font-family:Arial,sans-serif">In
                line with Implementation Guidance 13.6 from the </span><span style="font-size:11pt;font-family:Arial,sans-serif"><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf" target="_blank">New gTLD Subsequent Procedures Final
                  Report<span style="text-decoration-line:none"> </span></a>(pg.
                244), this implementation should enable the public to
                easily identify and obtain information about
                applications for closed generic gTLDs. The group agrees
                that there must be a centralized space where prospective
                commenters can go to understand the rules for closed
                generic gTLDs and view the applications themselves. <u></u><u></u></span></font></li>
          <li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline"><span style="font-size:11pt;font-family:Arial,sans-serif"><font color="#b45f06">Note: In arriving at this compromise
                approach to Public Comment, the group acknowledges the
                unique nature inherent to closed generic gTLDs, as well
                as the need for sufficient time for meaningful Public
                Comments, and the public’s need to readily find all
                relevant information about closed generic gTLD
                applications."</font></span></li>
        </ul>
      </li>
    </ul>
    <p>Best, Kathy <br>
      <font color="#b45f06"><span style="font-size:11pt;font-family:Arial,sans-serif"></span></font></p>
    <div>On 6/6/2023 11:03 AM, Sophie Hey wrote:<br>
    </div>
    <blockquote type="cite">
      
      
      
      
      <div>
        <p class="MsoNormal"><span style="font-size:11pt">Hi all,<u></u><u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt">I have
            attempted to come up with possible compromise language on
            public comments for 22.b of the Framework given the comments
            I saw on list the other day. This language attempts to take
            into consideration that feedback as well as: <u></u><u></u></span></p>
        <ul style="margin-top:0cm" type="disc">
          <li style="margin-left:0cm">
            <span style="font-size:11pt"><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf" target="_blank">SubPro</a> Implementation
              Guidance 13.6 (p 58, 244);<u></u><u></u></span></li>
          <li style="margin-left:0cm">
            <span style="font-size:11pt">SubPro Recommendation 20.4 (p
              91, 261) on 30-day operational public comment periods for
              application change requests;<u></u><u></u></span></li>
          <li style="margin-left:0cm">
            <span style="font-size:11pt">SubPro Recommendation 28.14
              (p 131, 280) on a single Public Comment;<u></u><u></u></span></li>
          <li style="margin-left:0cm">
            <span style="font-size:11pt">SubPro Recommendation 30.5 (p
              140, 283) on GAC Early Warnings running concurrently with
              the public comment period and the status of 30.5 as
              Pending in the Board’s
              <a href="https://www.icann.org/en/system/files/files/scorecard-subpro-pdp-board-action-16mar23-en.pdf" target="_blank">
                Scorecard</a> (p39) from <a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en#section2.a" target="_blank">
                16 March 2023</a>;<u></u><u></u></span></li>
          <li style="margin-left:0cm">
            <span style="font-size:11pt"><a href="https://www.icann.org/en/system/files/files/subpro-oda-12dec22-en.pdf" target="_blank">Operational Design Assessment</a>
              section 6.2.7 (p 213) stating that the public comment
              period will run for 90-days.<u></u><u></u></span></li>
        </ul>
        <p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt">Proposal:<u></u><u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt">22.b
            Applications for closed generics gTLDs must be subject to
            the same Public Comment period as all other gTLD
            applications set out in SubPro Final Report recommendation
            28.14.<u></u><u></u></span></p>
        <ol style="margin-top:0cm" type="i" start="1">
          <li class="MsoNormal"><span style="font-size:11pt">Consistent with SubPro
              Recommendation 20.4, change requests to closed generic
              gTLD applications in response to public comments,
              objections, whether formal or informal, GAC Consensus
              Advice, GAC Early Warnings, or other comments from the GAC
              who will be subject to an additional 30-day operational
              public comment period.
              <u></u><u></u></span></li>
          <li class="MsoNormal"><span style="font-size:11pt">In line with Implementation
              Guidance 13.6 from the
              <a href="https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf__;!!PtGJab4!_6G04zuduBJlatvxO1KXVdYeKGv57RsVaOoKh3W11SOt5UF6MyWvPL2vighBwDwaI6EKwoq-W8w-Gf5bKlKhC5tZd7TIGzYhf_MMVg$" target="_blank">
                New gTLD Subsequent Procedures Final Report
                [gnso.icann.org]</a>(pg. 244), this implementation
              should enable the public to easily identify and obtain
              information about applications for closed generic gTLDs.
              The group agrees that there must be a centralized space
              where prospective commenters can go to understand the
              rules for closed generic gTLDs and view the applications
              themselves. <u></u><u></u></span></li>
          <li class="MsoNormal"><span style="font-size:11pt">Any policy work on closed generic
              gTLDs must consider whether any other public comment
              period for closed generic gTLDs is appropriate, balancing
              the interests of applicants who may be in contention sets
              with Closed Generics, the applicant, and prospective
              commenters.
              <u></u><u></u></span></li>
        </ol>
        <p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt">Rationales:<u></u><u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt">22.b: We can
            all agree that closed generics are subject to the already
            established public comment period.
            <u></u><u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt">22.b.i:
            Expressly calling out change requests for closed generic
            gTLD applications in response to public feedback requiring a
            separate public comment period. I think that changes to
            closed generic gTLD applications would already be covered by
            20.4, but understanding a need for detail, I propose calling
            this out specifically.<u></u><u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt">22.b.ii:
            Making sure that there is outreach and information available
            to the public on closed generic gTLDs. I also did not see
            any push back to this language on list (apologies if I
            missed it).
            <u></u><u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt">22.b.iii:
            Committing to a policy discussion on an additional public
            comment period for closed generic gTLDs.
            <u></u><u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt">Sophie<u></u><u></u></span></p>
        <p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
        <div>
          <p class="MsoNormal"><span>Sophie Hey
              <br>
            </span><span>she/her</span><span><br>
            </span><span>Policy Advisor</span><span><br>
              Com Laude<br>
            </span><b><span>T</span></b><span> +44 (0) 20 7421 8250<br>
              <b><span style="color:rgb(149,7,52)">Ext</span></b> 252</span><span><br>
              <br>
            </span><a href="https://comlaude.com/" target="_blank"><span><img style="width: 0.4166in; height: 0.5694in;" id="m_4468971854722979448m_51499300458384957Picture_x0020_1" src="cid:188950cbd774cff311" width="40" height="55" border="0"></span></a><span style="font-size:11pt"><br>
              <br>
              <i>We are pleased to launch our <a href="https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADl_RQA0" target="_blank">
                  <span style="color:blue">new YouTube channel</span></a></i></span><span style="font-size:11pt"><img style="width: 0.0138in; height: 0.0138in;" id="m_4468971854722979448m_51499300458384957_x0000_i1025" src="https://t-uk.xink.io/Tracking/Impression/UxsAAGVfAADl_RQA0" alt="." width="1" height="1" border="0"></span><span style="font-size:11pt"><u></u><u></u></span></p>
        </div>
        <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">
                gnso-gac-closed-generics
                <a href="mailto:gnso-gac-closed-generics-bounces@icann.org" target="_blank"><gnso-gac-closed-generics-bounces@icann.org></a>
                <b>On Behalf Of </b>Melissa Peters Allgood<br>
                <b>Sent:</b> Tuesday, June 6, 2023 1:30 PM<br>
                <b>To:</b> <a href="mailto:gnso-gac-closed-generics@icann.org" target="_blank">gnso-gac-closed-generics@icann.org</a><br>
                <b>Subject:</b> [gnso-gac-closed-generics] Closed
                Generics Preparation for 7 June Meeting<u></u><u></u></span></p>
          </div>
        </div>
        <p class="MsoNormal"><u></u> <u></u></p>
        <div>
          <div>
            <p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US">Hello all,<u></u><u></u></span></p>
            <p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
              <span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US"> <u></u><u></u></span></p>
            <p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
              <span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US">I wanted to level-set after our call
                yesterday. I’ve emphasized a final push this week to get
                through your remaining work to ensure this group has the
                best opportunity possible to share a draft framework
                before the public sessions at ICANN77.<span> </span><u></u><u></u></span></p>
            <p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
              <span style="font-size:11pt;font-family:Arial,sans-serif;color:black;background:rgb(254,254,254)" lang="EN-US"> </span><span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US"><u></u><u></u></span></p>
            <p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
              <span style="font-size:11pt;font-family:Arial,sans-serif;color:black;background:rgb(254,254,254)" lang="EN-US">At the end of our call, we discussed that
                staff would take inputs on<span> </span><a href="https://docs.google.com/document/d/1nEy2mQm01ITo-ovxgIVQ0kNIpLqPV4bqVxTKgZb15vQ/edit" title="https://docs.google.com/document/d/1nEy2mQm01ITo-ovxgIVQ0kNIpLqPV4bqVxTKgZb15vQ/edit" target="_blank">Closed Generics Framework v4 –
                  Edits Tracked </a>forward. Staff has incorporated many
                of your suggestions and these are reflected in yellow
                highlight in the v4 – Edits Tracked document. A few
                comments remain in the v4 – Edits Tracked document and
                will be considered by the group on our 7 June call. <span> </span></span><span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US"><u></u><u></u></span></p>
            <p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
              <span style="font-size:11pt;font-family:Arial,sans-serif;color:black;background:rgb(254,254,254)" lang="EN-US"> </span><span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US"><u></u><u></u></span></p>
            <p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
              <span style="font-size:11pt;font-family:Arial,sans-serif;color:black;background:rgb(254,254,254)" lang="EN-US">To see the outcomes of your work in
                context, staff has compiled a<span> </span><a href="https://docs.google.com/document/d/1ZzjEiWbdkqOYbzoOPglwAn30qUUNRhjP8RmgKyTlgfQ/edit" target="_blank">Draft Framework for Closed
                  Generic gTLDs </a>that<span> </span>includes the
                edits discussed above, as well as an Executive Summary
                and annex of supporting reference material.<span> </span>Please note,
                22.b<span> </span>of the
                Draft Framework for Closed Generic gTLDs<span> </span>is holding for
                the outputs of your red line discussion of Public
                Comment.</span><span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US"><u></u><u></u></span></p>
            <p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
              <span style="font-size:11pt;font-family:Arial,sans-serif;color:black;background:rgb(254,254,254)" lang="EN-US"> </span><span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US"><u></u><u></u></span></p>
            <p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
              <span style="font-size:11pt;font-family:Arial,sans-serif;color:black;background:rgb(254,254,254)" lang="EN-US">Please review the Draft Framework for
                Closed Generic gTLDs in preparation for our 7 June call,
                as this is the complete draft framework, absent the
                Public Comment issue and a few outstanding points raised
                in the v4 – Edits Tracked document.</span><span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US"><u></u><u></u></span></p>
            <p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
              <span style="font-size:11pt;font-family:Arial,sans-serif;color:black;background:rgb(254,254,254)" lang="EN-US"> </span><span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US"><u></u><u></u></span></p>
            <p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
              <span style="font-size:11pt;font-family:Arial,sans-serif;color:black;background:rgb(254,254,254)" lang="EN-US">Agenda for 7 June:</span><span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US"><u></u><u></u></span></p>
            <ol style="margin-top:0cm" type="1" start="1">
              <li style="color:black;margin-left:0cm">
                <span style="font-size:11pt;font-family:Arial,sans-serif" lang="EN-US">Complete discussion of the Public Comment
                  red line topic<u></u><u></u></span></li>
              <li style="color:black;margin-left:0cm">
                <span style="font-size:11pt;font-family:Arial,sans-serif" lang="EN-US">Review remaining comments in v4 – Edits
                  Tracked<u></u><u></u></span></li>
              <li style="color:black;margin-left:0cm">
                <span style="font-size:11pt;font-family:Arial,sans-serif" lang="EN-US">Go/No Go decision on the Draft Framework<u></u><u></u></span></li>
              <li style="color:black;margin-left:0cm">
                <span style="font-size:11pt;font-family:Arial,sans-serif" lang="EN-US">ICANN77 Public Session planning<u></u><u></u></span></li>
            </ol>
            <p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
              <span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US"> <u></u><u></u></span></p>
            <p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
              <span style="font-size:11pt;font-family:Arial,sans-serif;color:black" lang="EN-US">Thank you for your continued efforts to
                collaborate and compromise.<u></u><u></u></span></p>
            <p class="MsoNormal"><span style="font-size:11pt" lang="EN-US"><u></u> <u></u></span></p>
          </div>
        </div>
        <p class="MsoNormal"><span lang="EN-US">Melissa<u></u><u></u></span></p>
      </div>
      <hr>
      The contents of this email and any attachments are confidential to
      the intended recipient. They may not be disclosed, used by or
      copied in any way by anyone other than the intended recipient. If
      you have received this message in error, please return it to the
      sender (deleting the body of the email and attachments in your
      reply) and immediately and permanently delete it. Please note that
      Com Laude Group Limited (the “Com Laude Group”) does not accept
      any responsibility for viruses and it is your responsibility to
      scan or otherwise check this email and any attachments. The Com
      Laude Group does not accept liability for statements which are
      clearly the sender's own and not made on behalf of the group or
      one of its member entities. The Com Laude Group is a limited
      company registered in England and Wales with company number
      10689074 and registered office at 28-30 Little Russell Street,
      London, WC1A 2HN England. The Com Laude Group includes Nom-IQ
      Limited t/a Com Laude, a company registered in England and Wales
      with company number 5047655 and registered office at 28-30 Little
      Russell Street, London, WC1A 2HN England; Valideus Limited, a
      company registered in England and Wales with company number
      6181291 and registered office at 28-30 Little Russell Street,
      London, WC1A 2HN England; Demys Limited, a company registered in
      Scotland with company number SC197176 and registered office at 15
      William Street, South West Lane, Edinburgh, EH3 7LL Scotland;
      Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation
      incorporated in the State of Washington and principal office
      address at Suite 332, Securities Building, 1904 Third Ave,
      Seattle, WA 98101; Com Laude (Japan) Corporation, a company
      registered in Japan with company number 0100-01-190853 and
      registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033,
      Japan; Com Laude Domain ESP S.L.U., a company registered in Spain
      and registered office address at Calle Barcas 2, 2, Valencia,
      46002, Spain. For further information see
      <a href="https://comlaude.com/" target="_blank">www.comlaude.com</a>
      <br>
      <fieldset></fieldset>
      <pre>_______________________________________________
gnso-gac-closed-generics mailing list
<a href="mailto:gnso-gac-closed-generics@icann.org" target="_blank">gnso-gac-closed-generics@icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics</a>

_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</pre>
    </blockquote>
    <pre cols="72">-- 
Kathy Kleiman
President, Domain Name Rights Coalition
</pre>
  </div>
_______________________________________________<br>
gnso-gac-closed-generics mailing list<br>
<a href="mailto:gnso-gac-closed-generics@icann.org" target="_blank">gnso-gac-closed-generics@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div>