<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 class=""><br class=""></div>Some comments inline:<div class=""><br class=""><div><blockquote type="cite" 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: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">a. Auctions: Mechanisms of Last Resort:<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_15S-5FsUuP-5FgmKqba26tU9kYQ8mVF76W-5F3CSl4raxSgvm8_edit-3Fusp-3Dsharing&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=QiF-05YzARosRvTYd84AB_UYInlydmFcjNmBM5XgySw&m=MIgsm29fz6Lyje9MgO3a4FzN-MoxjRUjlcbDF9MN8vk&s=kIFf-jf7ZObRYoubtCek94jCaVwb0YeSOFZPIqw4D7o&e=" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">https://docs.google.com/document/d/15S_sUuP_gmKqba26tU9kYQ8mVF76W_3CSl4raxSgvm8/edit?usp=sharing [docs.google.com]</a><o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt 72pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><ul type="disc" style="margin-bottom: 0cm; margin-top: 0cm;" class=""><li class="MsoListParagraphCxSpMiddle" style="margin-left: 18pt;">Discussion will continue of the list on the different options. Unless we stay with the status quo, this will likely need to go out for public comment.</li><li class="MsoListParagraphCxSpMiddle" style="margin-left: 18pt;"><o:p class=""></o:p></li></ul></div></blockquote><div><br class=""></div><div><br class=""></div>While the details are being sorted out, for me it's clear that a consensus on changing the rules of last resort contention resolution is forming. So we should look more into how it's changed, not if it is change. </div><div><br class=""><blockquote type="cite" 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;"><ul type="disc" style="margin-bottom: 0cm; margin-top: 0cm;" class=""><li class="MsoListParagraphCxSpMiddle" style="margin-left: 18pt;">Consideration - We have already ruled out other things that could have addressed collusion or profiting from the program – for example, we could have raised the application fee, or could have said that portfolio applicants are not allowed. We are potentially running out of options and this is what we are left with. It’s tricky and we may not completely be able to prevent the behavior.</li></ul></div></blockquote><div><br class=""></div>Raising the application fee goes both against the consensus on being a cost-recovery program and against applicants in underserved regions. </div><div><br class=""><blockquote type="cite" 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;"><ul type="disc" style="margin-bottom: 0cm; margin-top: 0cm;" class=""><li class="MsoListParagraphCxSpMiddle" style="margin-left: 18pt;"><o:p class=""></o:p></li></ul><div style="margin: 0cm 0cm 0.0001pt 54pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">b. Base Registry Agreement:<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_14HxLzQMXs90hAkpRStPAwHDC4CxaYXWqxZ-2DpsTmxHdU_edit-3Fusp-3Dsharing&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=QiF-05YzARosRvTYd84AB_UYInlydmFcjNmBM5XgySw&m=MIgsm29fz6Lyje9MgO3a4FzN-MoxjRUjlcbDF9MN8vk&s=kZOi3OtRDAgvG7qkhq24pOSAdCIn_KyEFn_pfUDFwx4&e=" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">https://docs.google.com/document/d/14HxLzQMXs90hAkpRStPAwHDC4CxaYXWqxZ-psTmxHdU/edit?usp=sharing [docs.google.com]</a><o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><ul type="disc" style="margin-bottom: 0cm; margin-top: 0cm;" class=""><li class="MsoListParagraphCxSpFirst" style="margin-left: 0cm;">Review of policy goals and high-level agreements.<o:p class=""></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left: 0cm;">Proposed high-level agreement would leave quite a bit of detail for the IRT to work out.</li></ul></div></blockquote><div><br class=""></div>My recent experience in the RegData Policy IRT is that even very detailed policy ends up generating lots of work, so I strongly recommend the WG to drill down the policies some more. </div><div><blockquote type="cite" 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;"><ul type="disc" style="margin-bottom: 0cm; margin-top: 0cm;" class=""><li class="MsoListParagraphCxSpMiddle" style="margin-left: 0cm;"><o:p class=""></o:p></li><li class="MsoListParagraphCxSpFirst" style="margin-left: 0cm;"><ul type="circle" style="margin-bottom: 0cm; margin-top: 0cm;" class=""><li class="MsoListParagraphCxSpMiddle" style="margin-left: 0cm;"><span style="" class="">If it’s a PIC, we need to reconcile with the groups that oppose PICs in general, although some of the concerns about PICs may be the name used – the term “public interest” may be a misnomer.</span><o:p class=""></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left: 0cm;"><span style="" class="">Proposal to suggest that this is included in PICs.<span class="Apple-converted-space"> </span></span></li></ul></li></ul></div></blockquote><div><br class=""></div>PIC is a misnomer, but that doesn't mean we shouldn't use it. Perhaps adding a note that PIC is a misnomer but leaving it at that instead of changing its name ? </div><div><br class=""><blockquote type="cite" 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;"><ul type="disc" style="margin-bottom: 0cm; margin-top: 0cm;" class=""><li class="MsoListParagraphCxSpFirst" style="margin-left: 0cm;"><ul type="circle" style="margin-bottom: 0cm; margin-top: 0cm;" class=""><li class="MsoListParagraphCxSpMiddle" style="margin-left: 0cm;"><o:p class=""></o:p></li></ul></li></ul><div style="margin: 0cm 0cm 0.0001pt 72pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class="">ACTION ITEM: Working Group members to respond on list to the proposal to add a Public Interest Commitment<span class="Apple-converted-space"> </span></b><b class=""><span style="" class="">stating that the registry operator will not engage in fraudulent and deceptive practices. Are there objections?</span></b><b class=""><span style="" class=""><o:p class=""></o:p></span></b></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="" class=""><o:p class=""> </o:p></span></b></div><ul type="disc" style="margin-bottom: 0cm; margin-top: 0cm;" class=""><li class="MsoListParagraphCxSpFirst" style="margin-left: 18pt;"><span style="background-color: white;" class="">Review of comment on registration terms, billing cycles, and presumptive renewals. In response to Google’s comment on this topic: the concerns should probably be addressed by asking for an exemption and providing a rationale. Otherwise there are mechanisms (SSAC, IETF – the EPP Protocol) to deal with these concerns, but this is outside of the WG’s area of expertise.</span></li></ul></div></blockquote><div><br class=""></div>We should also note that the RA doesn't cover the Rr relationship with the registrant, were most of these concerns should be placed. </div><div><br class=""><blockquote type="cite" 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;"><ul type="disc" style="margin-bottom: 0cm; margin-top: 0cm;" class=""><li class="MsoListParagraphCxSpFirst" style="margin-left: 18pt;"><o:p class=""></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left: 18pt;">Review of comments on premium pricing. Note that there was also an issue that SubPro had referred to RPMs – reservation of names that later go to premium pricing, and whether they go around RPMs.<o:p class=""></o:p></li><li class="MsoListParagraphCxSpMiddle" style="margin-left: 18pt;">There is a fine balance about whether issues related to premium pricing are in scope or not. We can say that transparency is key, that provisions in the agreement are there to require this transparency, and that ICANN should be enforcing the provisions of the RA and RAA.</li></ul></div></blockquote><div><br class=""></div>Picket fence is there to make the actual pricing out of scope. Pricing changes can be and currently are regulated by RA. </div><div><br class=""></div></div><div><br class=""></div><div><br class=""></div><div>Rubens</div><div><br class=""></div></body></html>