<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"><div>Dear IRT members,</div><div><br></div><div>In preparation for our next IRT meeting on Tue. 10 May, during which we would like to focus our discussion on the implementation of the transition from thin to thick, we would like to gather your thoughts on the open questions below.</div><div><br></div><div>A you may recall, these questions emanate from prior discussions on the mailing list regarding proposals for the transition of existing registration from thin to thick. For more background, please refer our presentation earlier this week (available at: <a href="https://community.icann.org/display/TWCPI/IRT+Meetings">https://community.icann.org/display/TWCPI/IRT+Meetings</a>).</div><div><br></div><div>Open questions :</div><div><ol><li>What would the a bulk transfer be under option 2 (proposal that registries do not impose checks or validation parameters on the registration data being transitioned from thin to thick) ?</li><li>How can we minimize the amount of “throw away code” ?</li><li>Should there be a minimal set of validation parameters ? For example: Numerical/Alphanumerical/UTF8 contraints on phone fields, requirement to provide Contact ID and Auth Info, a maximum length of fields</li><li>Should we aim to synchronize implementation of the new and existing registrations tracks ?</li><li>Once data is migrated, what rules should apply ? Should new and existing registrations be treated differently based on their creation date and the applicable RAA ?</li><li>Is the potential impact of option 2 on future transfers of registration acceptable ?</li></ol></div><div>Please provide your input in response to this email by Mon. 9 May COB in your time zone.</div><div><br></div><div><div>Best Regards</div><div><div>-- </div><div>Fabien Betremieux</div><div>Sr. Registry Services & Engagement Manager</div><div>Global Domains Division, ICANN</div></div></div></body></html>