You're viewing an archived page. It is no longer being updated.
Action List
The list was last updated 16 October 2025
| 71.2 | Marco, Erik, Job, Tim | To work on a method of cross authentication of autnum (possibly involving RPKI) |
Overtaken by events (Action on the NCC-Services-WG and NWI-5) |
| 71.1 | WW144 | To organise an effort to look at the fact that the original RFCset on RPSL has been overtaken by events and should be re-examined. | Discharged (Note: It was marked as ongoing at RIPE 72, but WW144 was not present there to report; a short discussion was initiated by him shortly after RIPE 71) |
| 70.2 | RIPE NCC | Come up with a proposal for the status: field to fix the requirement that certain objects may need multi-valued status |
Superseded by NWI-4 |
| 70.1 | All | Discuss deprecation of plain text passwords in email | Done ✓ |
| 69.3 | RIPE NCC | To examine and report on possible solutions to improving geolocation data in the RIPE DB | Overtaken by events (Decision by the RIPE NCC Executive Board not to support resource expenditure in the area of geolocation services) |
| 69.2 | RIPE NCC | Come up with some straw man proposals for displaying history for objects where available | Superseded by NWI-2 |
| 69.1 | RIPE NCC | Produce a self contained document describing migration of the changed: attribute to the last-modified:/created: attributes |
Discharged |
| 68.1 | RIPE NCC | Remove the "referral-by:" attribute | Discharged |
| 67.6 | WW144 → Job (at RIPE 69) | To bring to the attention of the Routing WG the fact that the routing data as recorded in the DB is generally very poor (Report by Alexander Azimov) | Discharged |
| 67.5 | WW144 | To check that the AntiAbuse Working Group has properly specified both what should be done with mail that is sent to the abuse contact and (possibly) its format. | Discharged (Note: Opened again, probably by mistake at RIPE69; Passed again onto AA-WG at RIPE70; Closed in DB-WG at RIPE72) |
| 67.4 | WW144 | Take the issue of geolocation to the RIPE NCC Services Working Group as it does not seem to be heavily used. | Subsumed into 69.3 |
| 67.3 | WW144 | To ensure that the next RIPE NCC Services Working Group (RIPE 68) includes a session on the operational aspects of running the RIPE Database. | Discharged |
| 67.2 | RIPE NCC | Implement changes as already announced to the release process and monitor feedback from community. | Done ✓ |
| 67.1 | RIPE NCC | Report on known bugs in the RIPE Database | Done ✓ |
| 66.5 | RIPE NCC | Check that all systems are UTF8 ready | Done ✓ |
| 66.4 | Piotr, NT13, WW144 | Raise issue of English translation requiring PDP with RIPE NCC Services WG and on the RIPE Database mailing list | Abandoned |
| 66.3 | RIPE NCC | Raise proposal about single sign-on on mailing list | Done ✓ |
| 66.2 | RIPE NCC | Raise proposal about route object cleanup on mailing list | Done ✓ |
| 66.1 | RIPE NCC | Clarify design goals with community | Done ✓ |
| 65.4 | RIPE NCC | Ensure that 2011-06 and its effects are fully documented before implementation. | Discharged |
| 65.3 | RIPE NCC | Investigate and report on data protection issues regarding history of database objects. | Done ✓ |
| 65.2 | RIPE NCC | Raise interest in geolocation attribute | Done ✓ (Superseded by 67.4) |
| 65.1 | RIPE NCC | Develop requirements with community for new resource-org object. | Discharged |
| 64.1 | RIPE NCC | Hiding maintainer md5 hash | Done ✓ |
| 63.3 | Dave Freedman | Raise issue of reverse lookup mechanism for non-orphaned aut-num objects with mailing list. | Dropped |
| 63.2 | RIPE NCC | Inquiry into making RIPE Database wholly UTF-8 safe. | Discharged |
| 63.1 | WW144 | Ask RIPE Chairman and mailing list whether geolocation proxy has to go through RIPE NCC Services WG. | Done ✓ |
| 62.5 | RIPE NCC | Implement the dash-notation changes for reverse DNS | Done ✓ |
| 62.4 | RIPE NCC | Do some analysis on the relative numbers of objects secured by passwords. | Done ✓ |
| 62.3 | RIPE NCC | Investigate use of TLS for whois data | Done ✓ |
| 62.2 | RIPE NCC | Examine use of Domain Object attributes | Done ✓ |
| 62.1 | RIPE NCC | Send proposal on geolocation to mailing list | Done ✓ |
| 61.3 | DB-WG | Community to think about better security for auth: (SHA-2 as a replacement for MD5) | Done ✓ |
| 61.2 | RIPE NCC | Investigate what the next appropriate level of password hash should be. | Done ✓ |
| 61.1 | RIPE NCC | Implement a very basic RFC 5943 compliant addition to the database. | Done ✓ |
| 60.2 | RIPE NCC | Come up with suggestions for other troubleshooting attributes | Done ✓ |
| 60.1 | DB-WG | Consider implications of ping-c attribute | Done ✓ |
| 59.7 | RIPE NCC | Investigate the Data Protection issues of allowing Key Cert searching | Overtaken by events (RESTful query facility) |
| 59.6 | WW114 | Refer question to NCC Services working group | Dropped |
| 59.5 | Piotr Strzyzewski | Raise the Key Cert Search proposal on the DB-WG mailing list | Overtaken by events (RESTful query facility) |
| 59.4 | RIPE NCC | Investigate amount of effort needed to implement Key Cert search | Overtaken by events (RESTful query facility) |
| 59.3 | RIPE NCC | Release the documentation in HTML form. | Discharged |
| 59.2 | RIPE NCC | Last notification of removal of orphan objects. | Done ✓ |
| 59.1 | RIPE NCC | Reverse delegation safeguards. | Done ✓ |
| 58.1 | RIPE NCC | Check that ASUSED can support IPv6 | Discharged |
| 57.2 | RIPE NCC | Cleanup of forward domain data | Done ✓ |
| 57.1 | RIPE NCC | Implement ASPLAIN. | Done ✓ |
| 56.1 | DP-TF | To consider the action to be taken when legal authority requests the removal of data from the database, and in particular whether records of such actions should be recorded. | Done ✓ |
| 55.3 | RIPE NCC | The RIPE NCC communications group to make it clear to external bodies what the function of the database actually is, and that removal from the database does not result in an associated resource disappearing. | Done ✓ |
| 55.2 | Peter Koch | To find out what the changed: line is used for and come up with a revised definition | Done ✓ |
| 55.1 | RIPE NCC | Add mnt-irt to the LIR Portal | Done ✓ |
| 54.7 | RIPE NCC | To prepare a plan for removal of the rev-srv attribute from the inetnum, inet6num objects. | Done ✓ |
| 54.6 | RIPE NCC | To summarise the discussion on orphaned objects and write up for the mailing list | Discharged |
| 54.5 | DB-TF | To analyse better the function of the country attribute in inetnum and inet6num. | Abandoned |
| 54.4 | RIPE NCC | To investigate the provision of a "white pages" facility for industry related persons. | Done ✓ |
| 54.3 | RIPE NCC | To go ahead and investigate ensuring that all objects are maintained, including timeline and notifications. Submit proposal to the Working Group. | Done ✓ |
| 54.2 | RIPE NCC + Chairs | To check through and decide how to split the Database manuals into RIPE and non-RIPE documents. | Done ✓ |
| 54.1 | RIPE NCC | To go ahead with final implementation of whois IRT query behaviour (-c), within 4 weeks. | Done ✓ |
| 53.4 | WW144 | Alert Routing WG about the implications of the ASN16 to ASN32 transition on tools. | Done ✓ |
| 53.3 | RIPE NCC | To make sure that if there is a "flag day" for ASN32 behaviour then the planning and introduction for this is done properly and advertised appropriately. | Done ✓ |
| 53.2 | RIPE NCC | To check and point out the requirement accept ASN32 systax to various software developers: including but not limited to irrtoolset, quagga etc. | Done ✓ |
| 53.1 | WW144 | Close AP50.1 (To make the country attribute on inetnum and inet6num optional and multiple) and properly reformulate it. | Done ✓ |
| 52.5 | RIPE NCC, WW144, Peter Koch | To produce a proposal, with timescales, for removing CRYPT-PW and circulate to the mailing list. | Done ✓ |
| 52.4 | RIPE NCC | To produce statistics showing how many objects are only protected by CRYPT-PW. | Done ✓ |
| 52.3 | WW144, NT14 | To reformulate irt: proposal and post to DB-WG mailing list | Done ✓ |
| 52.2 | RIPE NCC | To send their proposal to support enum delegations, using the nserver: attribute, to the WG-DB and DNS-DB mailing lists. | Done ✓ |
| 52.1 | WW144 | Put out a call for a task force to help the RIPE NCC in the task of updating the RIPE DB to compl with relevant Data Protection legislation. | Done ✓ |
| 51.9 | RIPE NCC | To contact a subset of the spam tool writers and make sure that they are aware of the change in behaviour as required by AP51.8 | Done ✓ |
| 51.8 | RIPE NCC | To properly implement DB behaviour to always return irt: object on address queries, if it exists. | Done ✓ |
| 51.7 | RIPE NCC | Make sure that the proposed DNS Security changes are implemented. | Done ✓ |
| 51.6 | Matt (ARIN) | To find out if any of the other routing registries have the ability to store RPSL-ng. RADB supports, APNIC nearly supports. Discharged. | Done ✓ |
| 51.5 | All | Check and see if there are any other missing IRIS attributes that are needed for the RIPE community. This should be on the whole community who should now be checking the IRIS server. | Done ✓ |
| 51.4 | RIPE NCC | Check that the mapping of contacts under IRIS is indeed not properly supported in IRIS (admin-c and tech-c). These attributes are actually supported. Discharged | Done ✓ |
| 51.3 | Peter Koch | Formulate a proposal on the mailing list to deprecate CRYPT-PW. Discharged. | Done ✓ |
| 51.2 | RIPE NCC | Check gnupgp compatibility before release of dated PGP signing functionality | Done ✓ |
| 51.1 | NT13 | To watch list, fold in updates to RIPE-50 minutes and release after 2 weeks. Discharged. | Done ✓ |
| 50.1 | Wilfried Woeber | Take proposal to make the country attribute optional and multiple for inetnum and inet6num objects to the mailing list. | Done - Superseded by 53.1 ✓ |
| 49.4 | RIPE NCC | To implement the abuse-email: attribute in the irt, person and role objects | Done ✓ |
| 49.3 | RIPE NCC | To produce a document detailing the programme for introducing the abuse contact changes | Done ✓ |
| 49.2 | RIPE NCC | Give updates about the number of abuse records in the database to the Working Group | Done ✓ |
| 49.1 | RIPE NCC, Anti-Spam WG | To convey new database abuse contact behaviour to the anti-spam tool writing community (RIPE-NCC has contacted over 100 people) | Done ✓ |
| 48.9 | RIPE NCC | To apply all available patches to RAToolset etc, and to start a rewrite in ANSI C | Done ✓ |
| 48.8 | RIPE NCC | RAToolset - To raise the issue on the appropriate mailing lists and seek advice on change of development model | Done ✓ |
| 48.7 | RIPE NCC | To make the PGP attribute optional on the IRT object | Done ✓ |
| 48.6 | RIPE NCC | To change DB behaviour to return IRT object | Done ✓ |
| 48.2 | Shane Kerr | To publish the CRISP/Joint-Whois requirements on the DB WG list | Done ✓ |
| 47.3 | RIPE NCC | Write a document properly documenting the use of the IRT object for reporting abuse. Covered by AP51.8. Superseded | Done ✓ |
| 46.5 | Wilfried Woeber | Coordinate with RIPE NCC to prepare a document summarizing basic assumptions about the use of the database. Presentation at RIPE 47 by WW14 | Done ✓ |