July 2018 - db-wg - mailman.ripe.net

WG Chair Selection
by William Sylvester 31 Jul '18

31 Jul '18

WG Members, This email kicks off the chair selection process for the open seat vacated last fall. With the new chair processes agreed to by the working group this will be a single chair seat for three years. This will migrate us into the new process where we will select one chair per year to maintain continuity and consistency for the chairs and prevent a situation like we have encountered previously where we were selecting chairs out of a drawing from a hat. As a reminder, chair terms are staggered yearly. The working group will select the chair by consensus. The process is as follows; This is the call for interested parties. Interested parties have two (2) weeks to make their interest known on this mailing list, or directly to the chair(s). After two weeks, the chair(s) ensure that all candidates are announced on the mailing list and issue a call for discussion. All members of the community are encourage to make a discussion and express their approval or otherwise of the presented candidates. Two (2) weeks after the call for discussion, the chair(s) declare a decision, based on mailing list discussion, as they would do for a policy proposal. All candidates please post to the mailing list at this time or contact the chairs (db-wg-chairs(a)ripe.net<mailto:db-wg-chairs@ripe.net>). Kind regards, William & Denis DB-WG Co-Chairs

4 3

Implementation plan and dates for NWI5 - Out-of-region ROUTE(6) objects and removal of ASN authorisation for ROUTE(6) object creation.
by Nathalie Trenaman 24 Jul '18

24 Jul '18

Dear colleagues, In February 2018, the RIPE Database Working Group reached consensus on NWI-5 - creating out of region ROUTE(6) objects in the RIPE Database. We will soon be making changes to the way out-of-region objects are handled in the RIPE Database. It's important that database users are aware of these changes and what they mean: 1. The RIPE Routing Registry will no longer support the creation of out-of-region ROUTE(6) and AUT-NUM objects 2. Existing out-of-region objects will have their "source:” attribute changed to "RIPE-NONAUTH” 3. The creation of ROUTE(6) objects will no longer need authorisation from the ASN holder We will implement these changes in the Release Candidate environment on Thursday, 2 August and go to full production on Tuesday, 4 September. Our implementation plan can be found at: https://www.ripe.net/manage-ips-and-asns/db/impact-analysis-for-nwi-5-imple… <https://www.ripe.net/manage-ips-and-asns/db/impact-analysis-for-nwi-5-imple…> The RIPE Database Working Group chairs also wrote a RIPE Labs article that describes the background of NWI-5: https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objec… <https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objec…> <https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objec… <https://labs.ripe.net/Members/denis/out-of-region-route-6-and-aut-num-objec…>> Please contact ,ripe-dbm(a)ripe.net <mailto:ripe-dbm@ripe.net>. if you still have questions after reading the implementation plan. Best regards, Nathalie Trenaman Product Manager RIPE NCC

6 7

Source GRS vs RIPE
by Aftab Siddiqui 18 Jul '18

18 Jul '18

Hi, I would like to understand the difference between these 2 results for the same prefix. Source: GRS https://apps.db.ripe.net/db-web-ui/#/query?bflag=true&source=GRS&searchtext… Source: RIPE https://apps.db.ripe.net/db-web-ui/#/query?bflag&searchtext=188.64.224.0%2F…

7 17