<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=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Em 10 de jul de 2019, à(s) 21:07:000, Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com" class="">AAikman@lrrc.com</a>> escreveu:</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: 12pt; font-family: "Times New Roman", serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Thank you Rubens. I guess you are saying that the rate of change to the root is not affected by the number of second level registrations that are live?</span></div></div></div></blockquote><br class=""></div><div>Exactly. Note also that delegation is not the only source of change in the root zone; if a TLD migrates from RSP A to RSP B, this is likely accomplished using a series of changes in order to not break the DNSSEC trust chain. A redelegation is more onerous from the root zone perspective than a delegation, and ICANN will need to factor that as well in keeping the "chicken soup" advice of rate of change. </div><div><br class=""></div><div><br class=""></div><div><br class=""></div><div>Rubens</div><div><br class=""></div><div><br class=""></div></body></html>