You are here: Home > Participate > Policy Development > Policy Proposals > Resource Authentication Key ( RAK ) code for third party authentication

This policy proposal has been withdrawn

Resource Authentication Key ( RAK ) code for third party authentication

The RIPE community requests that the RIPE NCC implement functionality that allows all number resources, in exacts and more specifics, to be authenticated via an date expiring API-key.

This service should be provided to all resource holders regardless of whether they are members or not. 

Get Involved

The RIPE NCC Services Working Group discusses the tools and services provided by the RIPE NCC, and conducts an ongoing evaluation of the RIPE NCC Activity Plan. The WG does not replace RIPE NCC Membership Meetings, and the RIPE NCC Budget and fee structures are beyond the scope of this WG. This mailing list was preceded by “impt-dev” which was a forum for the development of tools specifically for LIRs and is publicly archived on the RIPE NCC website. To post a message to the list, send an email to [email protected] Please note that only subscribers can post messages.

RIPE Forum

The RIPE Forum is an additional way to participate in RIPE community mailing list discussions using a web-based interface rather than an email client.

Check out the forum

Please contact if you need more information.

Stay up to date!

Follow @PDO_RIPE_NCC on Twitter.