<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi team,<div class=""><br class=""></div><div class="">During our call yesterday, we reviewed a few recommendations that included wording such as: <br class=""><div class=""><br class=""></div><div class=""><i class="">The Working Group recommends that the Registrar of Record MUST send a notification </i><b style="font-style: italic;" class="">[specify method of sending?] </b><i class="">to the RNH (as listed in the Registration Data at the time of the TAC request) … [emphasis added]</i></div><div class=""><br class=""></div><div class="">I suggest that we remove the bracketed wording, and follow the approach used for the ERRP. That consensus policy (at <a href="https://www.icann.org/resources/pages/errp-2013-02-28-en" class="">https://www.icann.org/resources/pages/errp-2013-02-28-en</a>) states:</div><div class=""><br class=""></div><div class=""><i class="">2.1.1 Prior to the expiration of any gTLD registration, registrars must notify the registered name holder of the expiration at least two times. One of these notices must be sent <b class="">approximately one month prior </b>to expiration and one must be sent <b class="">approximately one week prior</b> to expiration. [emphasis added]</i></div><div class=""><br class=""></div><div class="">After the formal sections of the policy, there is a notes section, which includes this:</div><div class=""><br class=""></div><div class=""><i class="">Expiration Reminder Notices: The policy recommendations by the GNSO recognize that some flexibility is required in the timing of pre-expiration renewal notices. As such, if the notices required to be sent approximately one month and one week prior to expiration described in paragraph 2.1.1 are transmitted <b class="">between 26-35 days</b> and <b class="">between 4-10 days prior to expiration</b>, respectively, this would be considered compliant with the policy. [emphasis added]</i></div><div class=""> </div><div class="">Using this approach, we can leave the wording as “send a notification” and then recommend that there is guidance in the notes, such as:</div></div><div class=""><br class=""></div><div class=""><i class="">Notification format: The policy recommendations by the GNSO recognize that notifications may be sent via email, SMS, or other secure messaging system. These examples are not intended to be limiting, and it is understood that additional methods of notification may be created that were not originally anticipated by the working group. </i></div><div class=""><i class=""><br class=""></i></div><div class=""><span style="font-style: normal;" class="">Happy to discuss via email or during a future call. </span></div><div class=""><span style="font-style: normal;" class=""><br class=""></span></div><div class=""><span style="font-style: normal;" class="">Regards,</span></div><div class=""><span style="font-style: normal;" class=""><br class=""></span></div><div class=""><span style="font-style: normal;" class="">Owen</span></div></body></html>