- db-wg - mailman.ripe.net

RIPE DB V2 (Perl) code
by Joao Luis Silva Damas 17 Mar '20

17 Mar '20

Does anyone have a copy of the Perl version of the RIPE DB code. I am looking for some code that I know was there and worked well (was fully debugged) but the RIPE FTP site no longer has v2 or v3 code that I can find (while it still has a copy of the WAIS source code!) So, does anyone have a copy that they can send around, please? Joao

1 1

RIPE Database E-Learning Course Launched
by Evelien Schilder 26 Feb '20

26 Feb '20

Dear RIPE Database Working Group, On behalf of the RIPE NCC Academy team, I would like to let you know that we have launched the updated RIPE Database e-learning course. Here are some of the major changes: - We modularised the content. You can now learn a new topic whenever you have 15 minutes to spare. - The modules are more interactive, and include practical exercises and scenarios. - The Training Database has been upgraded to the latest version of the RIPE Database software. The RIPE NCC Academy, our free, open e-learning platform has been revamped. It has received a visual upgrade. You can visit it at: https://academy.ripe.net <https://academy.ripe.net/> Kind regards, Evelien Schilder E-Learning Developer RIPE NCC

1 0

Update RIPE MNT records
by Mohamed Eldemiri 22 Feb '20

22 Feb '20

Hello RIPE support , In the past few years, our organization has gone through a privatization program by the government of Kuwait. Kuwait Stock Exchange has been changed now to Boursa Kuwait our old domain was kuwaitse.com is now boursakuwait.com.kw. The MNT ID and email is still pointing to old inaccessible domain ID, Anyway, the phone number & address are still the same, and the contact person still with Boursakuwait looped in this mail with his new email id 'ybaniyan(a)boursakuwait.com.kw'. Do you have any idea how to change these records? I have contacted the local registrar LR: Fast Telco and they said this must be done through the RIPE and they are not authorized to change these registration parameters. We will adhere to provide all the supporting official documents and memos that RIPE might asking for this change. LIR : Fast Telecommunications Company W.L.L. P.O.Box 287 15453 Dasman KUWAIT phone: +96522256666 fax: +96522401925 e-mail: ripeadmin (at) fasttelco (dot) net Areas serviced: KW 195.137.174.0/24 AS# 49104 Domain : BoursaKuwait.com.kw<https://dnslytics.com/bgp/as49104> % Abuse contact for '195.137.174.0 - 195.137.174.255' is 'abuse(a)fasttelco.net' inetnum: 195.137.174.0 - 195.137.174.255 netname: Kuwait-Stock-Exchange country: KW org: ORG-KSE1-RIPE admin-c: YA443-RIPE tech-c: YA443-RIPE status: ASSIGNED PI mnt-by: RIPE-NCC-END-MNT mnt-by: MNT-Kuwait-Stock-Exchange mnt-routes: MNT-Kuwait-Stock-Exchange mnt-domains: MNT-Kuwait-Stock-Exchange created: 2005-09-20T07:36:57Z last-modified: 2016-04-14T08:28:19Z source: RIPE # Filtered sponsoring-org: ORG-FTC1-RIPE organisation: ORG-KSE1-RIPE org-name: Kuwait Stock Exchange org-type: OTHER address: P.O. Box 22235 - Safat - Kuwait abuse-c: AR25180-RIPE mnt-ref: MNT-Kuwait-Stock-Exchange mnt-by: MNT-Kuwait-Stock-Exchange created: 2005-09-19T11:59:15Z last-modified: 2014-11-17T21:01:58Z source: RIPE # Filtered person: Yousef Abbas address: Kuwait City phone: +965 22992576 nic-hdl: YA443-RIPE created: 2009-07-27T06:57:06Z last-modified: 2016-04-06T19:52:01Z mnt-by: RIPE-NCC-LOCKED-MNT source: RIPE % Information related to '195.137.174.0/24AS49104' route: 195.137.174.0/24 descr: Kuwait Stock Exchange origin: AS49104 mnt-by: MNT-Kuwait-Stock-Exchange created: 2009-04-16T10:13:58Z last-modified: 2009-04-16T10:13:58Z source: RIPE Regards, Mohamed Eldemiri Network Administrator [cid:image001.png@01D5E970.A74CE0E0] Address: Mubarak Al Kabeer Street, Kuwait City, Kuwait P.O.Box: 22235, Safat, 13083 Kuwait Telephone: +(965) 2299-2595 Mobile: +(965) 55266079 Fax: +(965) 2244-0476 www.boursakuwait.com.kw Disclaimer: This e-mail message and any files attached to it are intended only for the recipients named above. The information in this e-mail is confidential and may be legally privileged. If you are not the intended recipient or have received this e-mail by error, you must not use or disseminate the information and must promptly notify the sender and delete this e-mail immediately. Unless otherwise explicitly provided in the body of this e-mail, neither this e-mail nor any attachment hereto is intended to operate as a commitment of whatever type or to include an electronic signature of whatever form under any applicable law. Opinions, conclusions and other information in this email that do not relate to the official business of Boursa Kuwait. Shall be understood as neither given nor endorsed by Boursa Kuwait. Although this email and any attachments are believed to be free of any virus or other defect, it is the responsibility of the recipient to ensure that it is virus free. Boursa Kuwait accepts no responsibility for any loss or damage arising in any way from the use of this email.

1 0

NWI-1 overview of abuse contacts for resources
by ripedenis＠yahoo.co.uk 21 Feb '20

21 Feb '20

Colleagues I said at Ripe 79 that I would review the open NWIs. So lets start with NWI-1. This has been open and virtually static since 2016. The original summary is here:https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005234.html The situation has changed since then with the "abuse-c:" attribute now allowed in resource objects. The main point I was making (as one of the authors of this NWI) is that there is no easy way for a resource holder to view all the abuse contact details for any of their resources. Hierarchical queries for abuse contacts only search 'up' the hierarchy. There is no easy way for the resource holder to search 'down' through the hierarchies to find all/any abuse contact details. These can now be added at any point in a hierarchy and forgotten about. But they are still active and may present the wrong information when people query for these details. The question now is "Do we need a search/query option or RIPEstat widget that will present an overview of all abuse contacts from a resource allocation down the hierarchy, or even for all of an organisation's resources?" cheers denis co-chair DB-WG

1 0

2018-06 Proposal Implemented (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
by Edward Shryane 31 Jan '20

31 Jan '20

Dear Working Group, The RIPE NCC Database team have now implemented the 2018-06 proposal (now ripe-731), "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up". We plan to deploy this to production on Wednesday 15th January. A nightly job will run from that evening onwards. We expect approximately 965 route objects will be initially marked for cleanup (which will happen 2 weeks after that). Regards Ed Shryane RIPE NCC > > From: Petrit Hasani <phasani(a)ripe.net> > Subject: [policy-announce] 2018-06 Proposal Accepted (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up) > Date: 6 November 2019 at 16:03:18 GMT+1 > To: policy-announce(a)ripe.net > > Dear colleagues, > > Consensus has been reached on 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up". > > This proposal aimed at creating a process to delete a non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA. > > You can find the full proposal at: > https://www.ripe.net/participate/policies/proposals/2018-06 > > The new RIPE Document is called ripe-731 and is available at: > https://www.ripe.net/publications/docs/ripe-731 > > We estimate that this proposal will take around two to three months to fully implement. > > We will send another announcement once the implementation is complete and the new procedures are in place. > > Thank you to everyone who provided us with your input. > > Kind regards, > > -- > Petrit Hasani > Policy Officer > RIPE NCC > > > > >

4 4

NWI-10 country attribute
by ripedenis＠yahoo.co.uk 27 Jan '20

27 Jan '20

Colleagues The chairs of the DB-WG declared a consensus on NWI-10 at RIPE 79. This is to add a "country:" attribute to the ORGANISATION object which will be managed by the RIPE NCC in ORGANISATION objects for resource holders. This email is to document that consensus and ask the RIPE NCC to implement this change. cheers denis co-chair DB-WG

2 1

RIPE Database Usage Survey - Database Requirements Task Force
by Boris Duval 20 Jan '20

20 Jan '20

Dear Colleagues, The RIPE Database Requirements Task Force (DBTF) needs your feedback! The DBTF has just launched a survey to know more about how the RIPE Community uses the RIPE databases. The results will provide feedback to the RIPE Database Task Force to help understand the relevance of the database to the RIPE Community and to help shape future RIPE Database policy. You can take the survey at: https://www.surveymonkey.com/r/PC9HTYP <https://www.surveymonkey.com/r/PC9HTYP> The deadline to answer the survey is 31 January. Feel free to share it with your network. Many thanks! Best, Boris Communications Officer RIPE NCC

1 0

NWI-9: Making the Whois NRTM Service Public
by Edward Shryane 16 Jan '20

16 Jan '20

Dear colleagues, Last month, as part of the DB-WG NWI-9 proposal, the RIPE NCC Executive Board resolved to make the Whois NRTM Service public. The full minutes of the Board meeting are on our website: https://www.ripe.net/about-us/executive-board/minutes/2019/minutes-130th-ri… We will now start working on all aspects related to implementing this decision and will have more details for you soon. Regards Ed Shryane RIPE NCC

2 1

database support for ed25519 PGP keys
by Marco d'Itri 19 Dec '19

19 Dec '19

Can RIPE staff clarify if there are plans to support PGP authentication of database updates using ed25519 keys? This should require not much more that upgrading gnupg to a modern release. -- ciao, Marco

2 1

converting a C class from PI to PA
by Franco Tauceri 19 Dec '19

19 Dec '19

Hello. What's the right how-to convert an existing C class from PI to PA? According to this: https://www.ripe.net/manage-ips-and-asns/ipv4/converting-pi-to-pa "Members can request this update via the LIR Portal." ... but I was not able to find HOW this may be done (If I try to edit the object, the field "status" is locked, and I can't edit it anyway... while I can edit other fields as usual) Regards -- Franco Tauceri DomainRegister m: 39.3483064202 w: https://DomainRegister.international e: franco.tauceri(a)domainregister.it

3 2