<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Dear colleagues,</div><div class=""><br class=""></div><div class="">Here is the impact analysis on the proposal to require the suffix '-MNT' when creating new MNTNER objects.</div><div class=""><br class=""></div><div class="">(1) Impact to Whois Update</div><div class=""><br class=""></div><div class="">When creating an MNTNER object, an additional syntax check will be performed on the MNTNER name to require an -MNT suffix.</div><div class=""><br class=""></div><div class="">If this suffix is not present in the MNTNER name, the create request will FAIL with an error:</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>***Error: Syntax error in <name></div><div class=""><br class=""></div><div class="">This error message is consistent with the existing syntax checks on the MNTNER name.</div><div class=""><br class=""></div><div class="">For this year so far, approximately 40% of all MNTNER objects created have an -MNT suffix. Database users will need to adjust how they create MNTNER objects to take this new rule into account.</div><div class=""><br class=""></div><div class="">This change will not affect existing MNTNER objects, which can be updated or deleted as before.</div><div class=""><br class=""></div><div class="">This change will also not affect references to MNTNER objects from other object types, an -MNT suffix will not be required on the mntner name.</div><div class=""><br class=""></div><div class="">(2) Impact to Whois Query</div><div class=""><br class=""></div><div class="">We do not expect any impact to Whois query.</div><div class=""><br class=""></div><div class="">(3) Impact to Existing Data</div><div class=""><br class=""></div><div class="">Approximately 36% of existing MNTNER objects are named without an -MNT suffix. No cleanup of existing data will be performed.</div><div class=""><br class=""></div><div class="">(4) Impact to Whois documentation</div><div class=""><br class=""></div><div class="">The RIPE NCC will also update the RIPE database documentation with the syntax change.</div><div class=""><br class=""></div><div class="">(5) Release timeline</div><div class=""><br class=""></div><div class="">We expect this change to take a short amount of time to implement, and will include the change in the Whois 1.99 release after the RIPE81 meeting.</div><div class=""><br class=""></div><div class="">As usual, we will deploy the release to the Release Candidate environment for 2 weeks before production, to allow for testing.</div><div class=""><br class=""></div><div class="">If you have any questions or feedback on this plan, please let me know.</div><div class=""><br class=""></div><div class="">Regards</div><div class="">Ed Shryane</div><div class="">RIPE NCC</div><div class=""><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On 30 Sep 2020, at 21:43, William Sylvester via db-wg <<a href="mailto:db-wg@ripe.net" class="">db-wg@ripe.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Monaco; 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; font-size: 12pt; font-family: Calibri, sans-serif;" class="">db-wg members,<span class="Apple-converted-space"> </span><o:p class=""></o:p></div><div style="margin: 0in; font-size: 12pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 12pt; font-family: Calibri, sans-serif;" class="">The chairs of the database working group believe there is a consensus to have a standardised name format for creating new MNTNER objects. There was talk of a prefix (MNT-) or a suffix (-MNT). When creating a new standard it doesn't really make sense to introduce a standard with multiple formats. As there are currently 36347 MNTNERs that end with -MNT and 12480 MNTNERs that start with MNT-, we suggest that the standard should be to end with -MNT.<o:p class=""></o:p></div><div style="margin: 0in; font-size: 12pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 12pt; font-family: Calibri, sans-serif;" class="">We ask the RIPE NCC to take the next steps in moving this request forward, conducting an impact analysis, and proceed with implementation.<o:p class=""></o:p></div><div style="margin: 0in; font-size: 12pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 12pt; font-family: Calibri, sans-serif;" class="">Best regards.<span class="Apple-converted-space"> </span><o:p class=""></o:p></div><div style="margin: 0in; font-size: 12pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 12pt; font-family: Calibri, sans-serif;" class="">William & denis<o:p class=""></o:p></div><div style="margin: 0in; font-size: 12pt; font-family: Calibri, sans-serif;" class="">db-wg chairs</div></div></div></blockquote></div><br class=""></body></html>