<div dir="auto"><div>Hi Stephanie,</div><div dir="auto">I believe the handbook is doable.</div><div dir="auto">We can always review such soon. </div><div dir="auto">- Akinbo. </div><div dir="auto"><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Fri, Mar 1, 2024, 4:43 PM Stephanie E Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>

  
  <div>
    <p>I believe I mentioned when we discussed this a while ago...I
      would like to see work on a handbook of registrants rights and
      obligations (with the emphasis on rights) recommence.  There have
      been a lot of changes in information policies since the last
      effort fizzled out around 15 years ago.  Bear in mind that many
      ordinary users buy their domains through resellers, and have no
      idea who the accredited registrars are, or who ICANN is for that
      matter.  Public information needs to be better, what better way
      than a handbook.  So no, we don't need just a policy status report
      on this stuff, we need a total review of how RNHs understand their
      rights and obligations.</p>
    <p>Yes, this demand is slightly off topic.  One has to do that when
      a longstanding need is being ignored....<br>
    </p>
    <p>cheers Stephanie Perrin<br>
    </p>
    <div>On 2024-02-29 8:14 p.m., Tomslin
      Samme-Nlar wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="auto">
        <div dir="auto">Dear members, </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">As described below, we have discussed the
          potential of the Council requesting a policy status report
          (PSR) in multiple PC calls over the past year. To help the
          Council decide, 3 sets of information were requested by or
          provided to the council.</div>
        <div dir="auto">1. Registrar input</div>
        <div dir="auto">2. ICANN compliance input</div>
        <div dir="auto">3. ICANN org Registrant Program</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Based on these, the Council must now decide to
          proceed with one of the following options. Please review and
          we will have a discussion at our PC meeting in San Juan this
          week on what NCSG thinks is the way to go:</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">1. Yes, after reviewing the materials, the
          Council would like to request a Policy Status Report.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">2. A Policy Status Report is not yet warranted.
          The Council believes further policy work on this is needed,
          but now is not the time due to current workload and
          prioritization of other more pressing work. We would like to
          revisit this decision in 2 years.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">3. No, the Council is not requesting a Policy
          Status Report at this time, as the policy seems to have been
          implemented as intended. The Council commits to reconsider
          this decision in 5 years. If ICANN org or a group within the
          ICANN community believe imminent work on these policies is
          necessary, they are welcome to address the GNSO Council, and
          we will reconsider this decision at that time.</div>
        <div dir="auto"><br>
        </div>
        <div data-smartmail="gmail_signature" dir="auto">Warmly, <br>
          Tomslin</div>
        <br>
        <div class="gmail_quote" dir="auto">
          <div dir="ltr" class="gmail_attr">---------- Forwarded message
            ---------<br>
            From: <strong class="gmail_sendername" dir="auto">DiBiase,
              Gregory via council</strong> <span dir="auto"><<a href="mailto:council@gnso.icann.org" target="_blank" rel="noreferrer">council@gnso.icann.org</a>></span><br>
            Date: Wed, 21 Feb 2024, 17:12<br>
            Subject: [council] ERRP/EDDP next steps<br>
            To: <a href="mailto:COUNCIL@GNSO.ICANN.ORG" target="_blank" rel="noreferrer">COUNCIL@GNSO.ICANN.ORG</a>
            <<a href="mailto:COUNCIL@gnso.icann.org" target="_blank" rel="noreferrer">COUNCIL@gnso.icann.org</a>><br>
          </div>
          <br>
          <br>
          <div link="#0563C1" vlink="#954F72" style="word-wrap:break-word" lang="EN-US">
            <div>
              <div>
                <p style="margin:0in"><span style="color:black">Dear
                    Councilors,</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"></span></p>
                <p style="margin:0in"><span style="color:black"> </span></p>
                <p style="margin:0in"><span style="color:black">We are
                    following up on our discussion regarding the Expired
                    Domain Deletion Policy (EDDP) and the Expired
                    Registration Recovery Policy (ERRP).</span> We are
                  deciding whether to request a Policy Status Report
                  reviewing these policies. When we looked at this issue
                  last year, ICANN Compliance noted some registrant
                  confusion around existing ERRP/EDDP policy and domain
                  renewal generally (see their report
                  <a href="https://mm.icann.org/pipermail/council/2022-November/026164.html" rel="noreferrer noreferrer" target="_blank">here</a>). In response,
                  Council requested information on what education
                  materials re: ERRP/EDDP policy currently exist (see
                  portion of original Council request below). During the
                  last Council meeting, Brian Gutterman from ICANN org
                  responded to this request from Council by outlining
                  the current resources available to registrants
                  regarding the ERPP/EDDP (see attached).<span style="font-size:12.0pt;font-family:"Times New Roman",serif"></span></p>
                <p style="margin:0in"><span style="color:black"> </span></p>
                <p style="margin:0in"><span style="color:black">Council
                    must now decide if it should request a Policy Status
                    Report on the ERRP/EDDP. As referenced above, we
                    have the following existing inputs to guide us:</span></p>
                <p style="margin:0in"><span style="color:black"> </span></p>
                <ol style="margin-top:0in" type="1" start="1">
                  <li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline">
                    <span style="font-size:7.0pt;color:black"> </span><span style="color:black">Registrars, who were asked to
                      flag substantial issues with the policies that
                      would warrant a near team request for policy
                      status report and did not note any issues</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"></span></li>
                  <li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline">
                    <span style="font-size:7.0pt;color:black"> </span><span style="color:black">ICANN Compliance, who provided
                      a</span><a href="https://mm.icann.org/pipermail/council/2022-November/026164.html" rel="noreferrer noreferrer" target="_blank"><span style="color:black;text-decoration:none">
                        write-up</span></a><span style="color:#0070c0">,
                    </span><span style="color:black">noting confusion
                      with key terms in the policy and persistent
                      registrant confusion with the auto-renew grace
                      period and aftermarket activities, <a href="http://et.al" rel="noreferrer noreferrer" target="_blank">et.al</a>.</span></li>
                  <li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline">
                    <span style="color:black">ICANN org Registrant
                      Program, provided a catalog of the available
                      educational resources on domain name expiration
                      and renewal</span> (Brian’s update at Council)</li>
                </ol>
                <p style="margin:0in"><span style="color:black"> </span></p>
                <p style="margin:0in"><span style="color:black">Plus any
                    other inputs your SOs/ACs are aware of and would
                    like to bring to Council’s attention.</span></p>
                <p style="margin:0in"><span style="color:black"> </span></p>
                <p style="margin:0in"><span style="color:black">Potential
                    options are:</span></p>
                <p style="margin:0in"><span style="color:black"> </span></p>
                <ol style="margin-top:0in" type="1" start="1">
                  <li style="margin-top:0in;margin-bottom:0in;margin-left:.25in;vertical-align:baseline">
                    <span style="color:black">Yes, after reviewing the
                      materials, the Council would like to request a
                      Policy Status Report.</span></li>
                  <li style="margin-top:0in;margin-bottom:0in;margin-left:.25in;vertical-align:baseline">
                    <span style="color:black">A Policy Status Report is
                      not yet warranted. The Council believes further
                      policy work on this is needed, but now is not the
                      time due to current workload and prioritization of
                      other more pressing work. We would like to revisit
                      this decision in 2 years.</span></li>
                  <li style="margin-top:0in;margin-bottom:0in;margin-left:.25in;vertical-align:baseline">
                    <span style="color:black">No, the Council is not
                      requesting a Policy Status Report at this time, as
                      the policy seems to have been implemented as
                      intended. The Council commits to reconsider this
                      decision in 5 years. If ICANN org or a group
                      within the ICANN community believe imminent work
                      on these policies is necessary, they are welcome
                      to address the GNSO Council, and we will
                      reconsider this decision at that time.</span></li>
                </ol>
                <p style="margin:0in"><span style="color:black"> </span></p>
                <p style="margin:0in"><span style="color:black">Please
                    review this material with your SOs/ACs and we will
                    revisit this topic at the April GNSO meeting.</span></p>
                <p style="margin:0in"><span style="color:black"> </span></p>
                <p style="margin:0in"><span style="color:black">Original
                    request from Council re: educational materials:</span></p>
                <p style="margin:0in;background:white"><span style="color:black"> </span></p>
                <p style="margin:0in;background:white"><span style="color:black">“<i>In recognition of the
                      reported ongoing registrant confusion, however,
                      the Council notes that additional guidance for
                      registrants may be appropriate. […] [T]he Council
                      would like to request further information from
                      ICANN org on what expiration-related educational
                      materials are currently published and whether
                      additional information can be provided (whether as
                      registrant educational material referenced in
                      Section 4.3 or elsewhere on ICANN’s website).
                      Receipt of this information will be helpful to the
                      Council in determining if updates to these
                      materials or additional material in other forms
                      could be helpful to combat the ongoing registrant
                      confusion.”</i></span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"></span></p>
                <p class="MsoNormal"> </p>
                <p class="MsoNormal">Thanks,</p>
                <p class="MsoNormal">Greg</p>
                <p class="MsoNormal"> </p>
                <p class="MsoNormal"> </p>
                <div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
                  <p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Caitlin
                      Tubergen <<a href="mailto:caitlin.tubergen@icann.org" rel="noreferrer noreferrer" target="_blank">caitlin.tubergen@icann.org</a>><br>
                      <b>Date: </b>Wednesday, February 14, 2024 at 3:36
                      PM<br>
                      <b>To: </b>"<a href="mailto:council@gnso.icann.org" rel="noreferrer noreferrer" target="_blank">council@gnso.icann.org</a>"
                      <<a href="mailto:council@gnso.icann.org" rel="noreferrer noreferrer" target="_blank">council@gnso.icann.org</a>><br>
                      <b>Cc: </b>Brian Gutterman <<a href="mailto:brian.gutterman@icann.org" rel="noreferrer noreferrer" target="_blank">brian.gutterman@icann.org</a>><br>
                      <b>Subject: </b>Re: [council] Summary of domain
                      name renewal and expiration educational resources
                      (Feb Council Agenda Item 6)</span></p>
                </div>
                <div>
                  <p class="MsoNormal"> </p>
                </div>
                <p class="MsoNormal">Dear Councilors,</p>
                <p class="MsoNormal"> </p>
                <p class="MsoNormal">Please find an updated attachment.
                </p>
                <p class="MsoNormal"> </p>
                <p class="MsoNormal">Apologies for the additional email.
                </p>
                <p class="MsoNormal"> </p>
                <p class="MsoNormal">Kind regards,</p>
                <p class="MsoNormal"> </p>
                <p class="MsoNormal">Caitlin</p>
                <p class="MsoNormal"> </p>
                <div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
                  <p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">council <<a href="mailto:council-bounces@gnso.icann.org" rel="noreferrer noreferrer" target="_blank">council-bounces@gnso.icann.org</a>>
                      on behalf of Caitlin Tubergen via council <<a href="mailto:council@gnso.icann.org" rel="noreferrer noreferrer" target="_blank">council@gnso.icann.org</a>><br>
                      <b>Reply-To: </b>Caitlin Tubergen <<a href="mailto:caitlin.tubergen@icann.org" rel="noreferrer noreferrer" target="_blank">caitlin.tubergen@icann.org</a>><br>
                      <b>Date: </b>Wednesday, February 14, 2024 at
                      10:07 AM<br>
                      <b>To: </b>"<a href="mailto:council@gnso.icann.org" rel="noreferrer noreferrer" target="_blank">council@gnso.icann.org</a>"
                      <<a href="mailto:council@gnso.icann.org" rel="noreferrer noreferrer" target="_blank">council@gnso.icann.org</a>><br>
                      <b>Cc: </b>Brian Gutterman <<a href="mailto:brian.gutterman@icann.org" rel="noreferrer noreferrer" target="_blank">brian.gutterman@icann.org</a>><br>
                      <b>Subject: </b>[council] Summary of domain name
                      renewal and expiration educational resources (Feb
                      Council Agenda Item 6)</span></p>
                </div>
                <div>
                  <p class="MsoNormal"> </p>
                </div>
                <p class="MsoNormal">Dear Councilors,</p>
                <p class="MsoNormal"> </p>
                <p class="MsoNormal">Further to Agenda Item 6 for
                  Thursday’s Council meeting, Next Steps for
                  Consideration of Expired Domain Deletion Policy
                  (“EDDP”) and Expired Registration Recovery Policy
                  (“ERRP”), please find a summary of the current
                  educational materials on domain name renewal and
                  expiration attached. </p>
                <p class="MsoNormal"> </p>
                <p class="MsoNormal">Brian Gutterman from ICANN org will
                  be providing an overview of the materials during the
                  Council meeting on Thursday.</p>
                <p class="MsoNormal"> </p>
                <p class="MsoNormal">Kind regards,</p>
                <p class="MsoNormal"> </p>
                <p class="MsoNormal">Caitlin</p>
              </div>
            </div>
          </div>
          _______________________________________________<br>
          council mailing list<br>
          <a href="mailto:council@gnso.icann.org" rel="noreferrer noreferrer" target="_blank">council@gnso.icann.org</a><br>
          <a href="https://mm.icann.org/mailman/listinfo/council" rel="noreferrer noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/council</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 noreferrer 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 noreferrer 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.</div>
      </div>
    </blockquote>
  </div>

</blockquote></div></div></div>