<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div class="content-isolator__container"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br><div><br><blockquote type="cite"><div>Em 14 de set. de 2023, à(s) 10:12, Jeff Schmidt <jschmidt@jasadvisors.com> escreveu:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><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: 400; 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; font-size: 11pt; font-family: Calibri, sans-serif;">Thanks! My intention is to have this discussion, so thanks for engaging. Like I said, nothing is impossible, but if we don’t address this (large) implication of our recommendations, I don’t think we have done our work.<o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">I’m not sure I understand your sheet. Let me simplify:<o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">Current root size: 1589<o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">5%: 80<o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">So we can add 80 TLDs to the root m/m. Plus or minus. I didn’t address “compounding” but you get the gist.</div></div></div></blockquote><div><br></div>I normalized to a per week %, which is why there is 1.2% (not 1.25% due to compounding). </div><div>I also only listed the total number of TLDs at that point considering the rate described, so the difference between week 0 and week 1 are 20 TLDs for 2012 guidance, 19 for 5% m/m, 8 to account for double delegation and some room for ordinary changes to the root zone. </div><div><br></div><div>That ramps up over the years; it reaches 35 a week after 1 year. I added per week columns to all scenarios to ease up the comparison. <br><blockquote type="cite"><div><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: 400; 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; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">1. That’s a lot. We need to check with IANA-Verisign and at least give them a courtesy heads-up and get their thoughts.</div></div></div></blockquote><div><br></div>Which is I what mentioned… these figures are only looking at the 5% a month root zone change rate. </div><div><br><blockquote type="cite"><div><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: 400; 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; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">2. That’s not a lot. If we have 1200 unique strings to research (same as 2012), that will take 15 months just to delegate to the TRT.</div></div></div></blockquote><div><br></div>It will reach 1200 in week 48, so it would be 11 months. But considering the 400/batch ICANN Org mentioned in the ODP, that takes 23 weeks, or 6 months. </div><div><br><blockquote type="cite"><div><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: 400; 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; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">3. This doesn’t address “normal” work to include routine RZCR which IANA-Verisign would still need to complete. That’s additional work on top of all of this.</div></div></div></blockquote><div><br></div>Which is why I used 0.5% instead of 0.6%. This assumes delegation of new TLDs (either to NTP or to registry) takes up 80% of available capacity keeping 20% pre-reserved for routine changes. </div><div><br></div><div>It’s also to be expected that if routine changes require more root zone change, new TLDs are the ones who get throttled. </div><div><br><blockquote type="cite"><div><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: 400; 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; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">4. This doesn’t address the RZCRs that would re-delegate away from the TRT to the new Registry along the way. That’s additional work on top of all of this.</div></div></div></blockquote><div><br></div>This is why is not 1.2% every week, to account for the additional move. But I am being too conservative to slow to 0.5% from the very beginning, when this would only be required by the time strings transition to delegation. </div><div><br></div><div><br></div><div><br></div><div>Rubens</div><div><br></div></div></div></body></html>