<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=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear Julie, <div class=""><br class=""></div><div class="">please find my comments below</div><div class="">1. the text:</div><div class=""><br class=""></div><div class=""><span id="docs-internal-guid-7bb484fa-7fff-dbdd-f09d-f839e2d37b68" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; vertical-align: baseline; white-space: pre-wrap;" class="">"or discouraging the use of the Sunrise Period by trademark owners"</span></span></div><div class=""><br class=""></div><div class="">contradicts the current ICANN practice of forcing Registries to reserve domain names due to </div><div class="">Names Collision Mitigation periods, where Registries have no freedom of denial to such requirements.</div><div class=""><br class=""></div><div class="">2. </div><div class="">There are no descriptions of how discouragement is measured, so it is non objective and there</div><div class="">is no way to predict for Registry if they follow the suggested language or not.</div><div class=""><br class=""></div><div class="">3.The text of the Context part does not mention existence of Landrush periods during the General Availability periods</div><div class="">where prices are significantly higher than during the later parts of the General Availability period (gradual decreasing of prices), </div><div class="">it is important to avoid misunderstanding and confusion among readers.</div><div class=""><br class=""></div><div class="">4. in the text "<span style="font-family: Calibri, sans-serif; font-size: 11pt; white-space: pre-wrap;" class="">including excessive pricing of Sunrise domains</span>" word excessive is a non objective marker, </div><div class="">the wording of significantly should be used (to avoid situation where ICANN or a panel will be deciding on the prices , which itself will cause </div><div class="">concerns of anti-monopoly agencies).</div><div class=""><br class=""></div><div class="">5. The text still have no safeguards for GEO TLDs, we do not know yet if the next iteration of ALP is going to be better than the current poor implementation, thus reservation of domains should not be a marker of a bad behavior.</div><div class=""><br class=""></div><div class="">P.s: I do not support the suggested edits of #2 proposed by the group (the previous version of Sunrise #2 was more clear, balanced)</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal; border-spacing: 0px; -webkit-text-decorations-in-effect: none; font-size: 11px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Sincerely Yours,<br class=""><br class="">Maxim Alzoba<br class="">Special projects manager,<br class="">International Relations Department,<br class="">FAITID<br class=""><br class="">m. +7 916 6761580<span style="text-align: -webkit-auto;" class="">(+whatsapp)</span></div><div class="">skype oldfrogger</div><div class=""><br class=""></div><div class="">Current UTC offset: +3.00 (.Moscow)</div></div></span></div></div></div></div></div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 22 Sep 2020, at 23:09, Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" class="">julie.hedlund@icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Dear All,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><i class="">Please see the action item below and post any comments to this list ASAP.<o:p class=""></o:p></i></b></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Kind regards,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Mary, Ariel, and Julie<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-size: 12pt;" class="">From:<span class="Apple-converted-space"> </span></span></b><span style="font-size: 12pt;" class="">GNSO-RPM-WG <<a href="mailto:gnso-rpm-wg-bounces@icann.org" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">gnso-rpm-wg-bounces@icann.org</a>> on behalf of Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">julie.hedlund@icann.org</a>><br class=""><b class="">Date:<span class="Apple-converted-space"> </span></b>Thursday, September 17, 2020 at 5:07 PM<br class=""><b class="">To:<span class="Apple-converted-space"> </span></b>"<a href="mailto:gnso-rpm-wg@icann.org" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">gnso-rpm-wg@icann.org</a>" <<a href="mailto:gnso-rpm-wg@icann.org" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">gnso-rpm-wg@icann.org</a>><br class=""><b class="">Subject:<span class="Apple-converted-space"> </span></b>[GNSO-RPM-WG] ACTION ITEM: Sunrise Recommendation #2 and Small Team 2 Suggested Language:<o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Dear All,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Please see the action item below from the WG meeting on 17 September:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Sunrise Recommendation #2 and Small Team 2 Suggested Language:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="" class="">ACTION ITEM: Discuss WG suggested revisions to the Recommendation and Implementation Guidance along with the suggested language from Small Team 2.</span></b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Please see the suggested revisions to Sunrise Recommendation #2 in the Google document at:<span class="Apple-converted-space"> </span><a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/12w5W2bQcviAqLwoDVB0vVK0n7SKj3fzP48NQyEW-1Q4/edit?usp=sharing__;!!PtGJab4!vwikSt_HHDU8CpTsVTNpVCKvvhfkw3RoDuQLZC9tK3qSp9Flz3aJeVIjw0KrKyJ30-ZjAqWjOA$" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">https://docs.google.com/document/d/12w5W2bQcviAqLwoDVB0vVK0n7SKj3fzP48NQyEW-1Q4/edit?usp=sharing [docs.google.com]</a>.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Please also review the following Suggested Language from Small Team:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><u class=""><span style="" class="">Suggestion Language from Small Team 2</span></u><span style="" class="">: “Implementation Guidance to Sunrise Recommendation 2: The IRT should explore the possibility of a third party challenge mechanism as one of the possible means, among others (for example, direct enforcement by ICANN Compliance) to implement this Recommendation to enforce the implementation of this recommended new RA provision. Any such third party challenge mechanism should include appropriate safeguards for registries.”</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><i class="">Please post any comments or questions for discussion to this list ASAP.</i></b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Kind regards,<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Mary, Ariel, and Julie<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-size: 12pt;" class="">From:<span class="Apple-converted-space"> </span></span></b><span style="font-size: 12pt;" class="">GNSO-RPM-WG <<a href="mailto:gnso-rpm-wg-bounces@icann.org" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">gnso-rpm-wg-bounces@icann.org</a>> on behalf of Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">julie.hedlund@icann.org</a>><br class=""><b class="">Date:<span class="Apple-converted-space"> </span></b>Thursday, September 17, 2020 at 2:49 PM<br class=""><b class="">To:<span class="Apple-converted-space"> </span></b>"<a href="mailto:gnso-rpm-wg@icann.org" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">gnso-rpm-wg@icann.org</a>" <<a href="mailto:gnso-rpm-wg@icann.org" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">gnso-rpm-wg@icann.org</a>><br class=""><b class="">Subject:<span class="Apple-converted-space"> </span></b>[GNSO-RPM-WG] Notes and Action Items: RPM PDP WG Meeting 17 September 2020</span><o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">Dear All,</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; caret-color: rgb(0, 0, 0); font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;" class=""><span style="" class=""> </span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; caret-color: rgb(0, 0, 0); font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;" class=""><span style="" class="">Please see below the action items captured by staff from the<span class="apple-converted-space"> </span></span>RPM PDP Working Group<span style="" class=""><span class="Apple-converted-space"> </span>call held on</span><span class="Apple-converted-space"> </span>17 September 2020 at 17:00 UTC<span style="" class="">. Staff<span class="Apple-converted-space"> </span></span>will post<span style="" class=""><span class="Apple-converted-space"> </span>these to the wiki space. <b class=""><i class="">Please note that these<span class="Apple-converted-space"> </span></i></b></span><b class=""><i class="">are<span style="" class=""><span class="Apple-converted-space"> </span>high-level notes and are not meant as a substitute for the recording</span>, chat room, or transcript</i></b><i class=""><span style="" class="">.</span></i><span style="" class=""> The recording, Zoom chat,</span><span class="Apple-converted-space"> </span>transcript<span style="" class=""><span class="Apple-converted-space"> </span>and attendance records are posted on the wiki<span class="apple-converted-space"> </span>at</span>:<span class="Apple-converted-space"> </span><a href="https://community.icann.org/display/RARPMRIAGPWG/2020-09-17+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">https://community.icann.org/display/RARPMRIAGPWG/2020-09-17+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG</a>.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">Best Regards,</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; caret-color: rgb(0, 0, 0); font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;" class="">Julie<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; caret-color: rgb(0, 0, 0); font-variant-caps: normal; text-align: start; -webkit-text-stroke-width: 0px; word-spacing: 0px;" class="">Julie Hedlund, Policy Director<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class=""> </span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class="">==</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 10pt; font-family: Arial, sans-serif;" class=""> </span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">NOTES & ACTION ITEMS</b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">Actions:</b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Sunrise Recommendation #2 and Small Team 2 Suggested Language:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="" class="">ACTION ITEM: Discuss WG suggested revisions to the Recommendation and Implementation Guidance along with the suggested language from Small Team 2.</span></b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="" class=""> </span></b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Suggested Language from Small Team 1 on ALP relating to Sunrise Questions #3 and #4:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">ACTION ITEM: Staff will check with GDS to see if this recommendation is feasible.</b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="" class=""> </span></b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">URS Final Recommendation (was #1):<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">ACTION ITEM: Minor change in the contextual language – change from “<span style="" class="">the Working Group affirms” to “the Working Group further notes”.</span></b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="" class=""> </span></b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">New URS Final Recommendation:</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">ACTION ITEM: Remove the quoted text from<span class="Apple-converted-space"> </span><span style="" class="">Purpose 6-PA5 and move it to a footnote for reference.</span></b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">Notes:</b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">1. Updates to Statements of Interest: No updates provided.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">2. Sunrise Recommendation #2 and Small Team 2 Suggested Language; see: <a href="http://mm.icann.org/pipermail/gnso-rpm-wg/2020-September/004503.html" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">Suggested Language from Small Team 2</a> and<a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/12w5W2bQcviAqLwoDVB0vVK0n7SKj3fzP48NQyEW-1Q4/edit?usp=sharing__;!!PtGJab4!vrG9bvGPh6CAcYH6gGtmazbvnCJsGe-fWqDidShS5tf9gWqE4k8oCMDj3vR6cqfVi26trKkD_g$" title="https://urldefense.com/v3/__https://docs.google.com/document/d/12w5W2bQcviAqLwoDVB0vVK0n7SKj3fzP48NQyEW-1Q4/edit?usp=sharing__;!!PtGJab4!vrG9bvGPh6CAcYH6gGtmazbvnCJsGe-fWqDidShS5tf9gWqE4k8oCMDj3vR6cqfVi26trKkD_g$" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">https://docs.google.com/document/d/12w5W2bQcviAqLwoDVB0vVK0n7SKj3fzP48NQyEW-1Q4/edit?usp=sharing [docs.google.com]</a><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Concerns raised by Maxim Alzoba about the two examples that they are too broad.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Further to my point, as was noted earlier, this is a high-level policy recommendation; the IRT will be tasked with implementing this recommendation and our guidance should be sufficient to allow the IRT to craft an appropriately tailored RA amendment and (hopefully a challenge mechanism with appropriate safeguards built in so as to not inhibit legitimate registry activities<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- I agree (I think) with Jason insofar as implementing this recommendation may necessitate a third party challenge mechanism akin to the PDDRP or pICDRP so aggrieved TM owners can challenge a registry activity and there can be a ruling as to whether the activity is legitimate or not.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Concerns about misinterpretation if we are not clear.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Perhaps we can just add a third bullet that says, “registry activities that have a bona fide legitimate basis or rationale are explicitly not intended to be inhibited by this provision”.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- As a staff suggestion for your consideration — perhaps we can include something to this effect: “The Working Group notes that this recommendation is not intended to preclude or restrict Registry operator’s legitimate business practice and pricing practice that are compliant with ICANN policies and procedures.”?<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Add to bullet point 1 (slightly revised)-- adding: "without countervailing rationale and/or reasonable activity by registries, including handling of dictionary terms.”<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Suggest addition to the Recommendation: “<span style="" class="">The Working Group recommends that the Registry Agreement for future new gTLDs include a provision stating that a Registry Operator shall not operate its TLD in such a way as to have the effect of [intentionally] circumventing the mandatory RPMs imposed by ICANN or restricting brand owners’ reasonable use of the Sunrise rights protection mechanism.” Text in brackets.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">-- Don’t think adding “intentionally” in the rec helps us because it doesn’t really address Maxim’s concern, because reserving a name intentionally as part of an ALP or something is still intentional.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class=""> </span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="" class="">ACTION ITEM: Discuss suggested language from Small Team 1 on the list.</span></b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class=""> </span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><u class=""><span style="" class="">Suggestion Language from Small Team 2</span></u><span style="" class="">: “Implementation Guidance to Sunrise Recommendation 2: The IRT should explore the possibility of a third party challenge mechanism as one of the possible means, among others (for example, direct enforcement by ICANN Compliance) to implement this Recommendation to enforce the implementation of this recommended new RA provision. Any such third party challenge mechanism should include appropriate safeguards for registries.”</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><i class=""><span style="" class="">-- Why would the proposed additional implementation guidance language be a beneficial addition to the existing implementation guidance</span></i><span style="" class="">? Answer: Takes some of the burden off of Compliance.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 12pt;" class=""> </span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><i class=""><span style="" class="">-- Does the phrase “explore the possibility of a third party challenge mechanism” encompass and authorize the IRT’s adoption and implementation of such a mechanism if it is found to be possible?</span></i><span style="" class=""> Answer: To amend the language to “explore and if possible implement”.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class=""> </span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><i class=""><span style="" class="">-- Would the challenge mechanism be operative against ICANN, a registry alleged to have circumvented a RPM, or both</span></i><span style="" class="">? Answer: It would be against the registry that is alleged to have circumvented it. There already is a way to challenge staff and Board actions.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><i class="">-- This would not be a mechanism as a way for ICANN Org Compliance to enforce – this would be a separate mechanism?</i> Answer: Correct.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><u class="">Discussion</u>:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Opposed to this language. Sunrise Rec #2 itself is still vague. <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Registries agree by contract to comply, but IRTs cannot develop consensus policies or revise contract terms – so this is out of scope.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- This is putting one vagueness on top of another.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- What authority does an IRT have to do these types of things.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Didn't an IRT create the URS, PDDRP, PICDRP, to name a few?<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Sunrise Rec #2 seems to beg for a third-party challenge mechanism.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- 1. Clause could include a clause to include a challenge mechanism. 2. IRTs do this sort of thing all the time (e.g. the AGB and all of the challenge mechanisms with it).<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Idea is that there would be an independent panel that an aggrieved party could go to – so not relying on ICANN Compliance and could be an independent review.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Why isn't a complaint to ICANN compliance sufficient here? I agree with David that it's especially problematic to move from "vague standard applied by single decisionmaker" to "vague standard applied by various possible decisionmakers"<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Would this be a time-sensitive mechanism?<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Because in response to the complaints over the years on sunrise circumvention, ICANN has consistently said they could do nothing about it.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Circumvention itself is not defined, so cannot be enforced.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- ICANN compliance would need to have a role, in a similar way it does in a PICDRP for instance; an independent panel would actually perform the substantive review and ICANN compliance would implement a panel finding, for example.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- If Rec 2 is "start doing something about it" then why isn't ICANN compliance the appropriate place?<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- URS and PDDRP are not Consensus Policy either. They were created during implementation of the 2007 GNSO PDP on New gTLDs.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Divergence in the WG on this suggested text.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">ACTION ITEM:<span class="Apple-converted-space"> </span><b class=""><span style="" class="">Discuss the suggested language on the list.</span></b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">3. Suggested Language from Small Team 1 on ALP relating to Sunrise Questions #3 and #4; see:<span class="Apple-converted-space"> </span><a href="http://mm.icann.org/pipermail/gnso-rpm-wg/2020-September/004505.html" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">http://mm.icann.org/pipermail/gnso-rpm-wg/2020-September/004505.html</a><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">“The Working Group recommends guidance to the Implementation Review Team that the Approved Launch Program (ALP) Application Review Guidelines be reviewed and clarified in order to address feedback obtained by the working group regarding the length of time and complexity of process involved in seeking to obtain approval for an ALP, and in particular recommends that the IRT consider the following:<br class="">1. Where ICANN can not make a determination regarding an ALP application it will notify the Registry Operator to that effect within 45 days stating explicit reasons for needing more time and further, provide a decision date projection plan within a time period not to exceed another 30 days. There should be a reasonable expectation that all negotiations should be completed within a 7 month period.<br class="">2. Where ICANN determines to decline an ALP application or make a request for further information ICANN will include a full explanation of the aspects of the ALP application ICANN deems to be acceptable and the aspects ICANN deems to be unacceptable.”<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><u class="">Discussion</u>:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- The reference to an ALP being adopted is in the TMCH procedures if approved it is outside of or in contravention of Sunrise. This is directly related to the operation of the Sunrise.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- TMCH RPMs Requirements document that is incorporated by reference into the AGB and the RA (<a href="http://newgtlds.icann.org/en/about/trademark-clearinghouse/rpm-requirements-14may14-en.pdf" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">http://newgtlds.icann.org/en/about/trademark-clearinghouse/rpm-requirements-14may14-en.pdf</a>). 4.5 deals with Launch Programs, specifically 4.5.2:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Registry Operator MAY, prior to the start date of its Sunrise Period, apply to ICANN for approval to conduct a registration program not otherwise permitted by these TMCH Requirements. Such a registration program application could, for example, provide for authorization to implement programs set forth in Registry Operator’s application for the TLD, which, if set forth in reasonable detail in the application for the TLD, will carry a presumption of being approved, unless ICANN reasonably determines that such requested registration program could contribute to consumer confusion or the infringement of intellectual property rights. If Registry Operator seeks ICANN’s approval of a program under this Section 4.5.2, and such requested registration program is substantially similar to a...”<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">ACTION ITEM: Staff will check with GDS to see if this recommendation is feasible.</b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">4. URS Final Recommendations; see: <a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1huKNcgg3VAk95oybb-7u9papLZ4kEMUHNQNElMPWMFY/edit?usp=sharing__;!!PtGJab4!vrG9bvGPh6CAcYH6gGtmazbvnCJsGe-fWqDidShS5tf9gWqE4k8oCMDj3vR6cqfVi25zeqf2-g$" style="color: rgb(5, 99, 193); text-decoration: underline;" class="">https://docs.google.com/document/d/1huKNcgg3VAk95oybb-7u9papLZ4kEMUHNQNElMPWMFY/edit?usp=sharing [docs.google.com]</a><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">a. URS Final Recommendation (was #1):<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Recommendation language stays as is.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Contextual language – inserted text to reflect the WG’s agreement to include the EPDP Phase 1 Recommendation #27 Wave 1 Report.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">ACTION ITEM: Minor change in the contextual language – change from “<span style="" class="">the Working Group affirms” to “the Working Group further notes”.</span></b><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class=""> </span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">b. New URS Final Recommendation:</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class=""> </span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">-- This is based on URS Question 1.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">-- It is a new recommendation based on responses received in the public comment.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">-- The context comes from the WG discussion of URS Question 1.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">-- The public comment review is based on the discussion of URS Question 1 and suggestion for a recommendation.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><u class="">Discussion</u>:<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Questions about the contextual language. Concern that the reference to<span class="Apple-converted-space"> </span><span style="" class="">Purpose 6-PA5</span><span class="Apple-converted-space"> </span>is somehow binding.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">-- Staff noted that it is not binding and there was no change to the new recommendation resulting from the WG’s review of the<span class="Apple-converted-space"> </span><span style="" class="">ICANN org’s EPDP Phase 1 Recommendation #27 Wave 1 Report</span>.<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">ACTION ITEM: Remove the quoted text from<span class="Apple-converted-space"> </span><span style="" class="">Purpose 6-PA5 and move it to a footnote for reference.</span></b><o:p class=""></o:p></div></div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">GNSO-RPM-WG mailing list</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="mailto:GNSO-RPM-WG@icann.org" style="color: rgb(5, 99, 193); text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">GNSO-RPM-WG@icann.org</a><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" style="color: rgb(5, 99, 193); text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">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 (</span><a href="https://www.icann.org/privacy/policy" style="color: rgb(5, 99, 193); text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">https://www.icann.org/privacy/policy</a><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">) and the website Terms of Service (</span><a href="https://www.icann.org/privacy/tos" style="color: rgb(5, 99, 193); text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">https://www.icann.org/privacy/tos</a><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">). 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.</span></div></blockquote></div><br class=""></div></div></div></div></div></div></body></html>