LACNIC Resource Certification System, RPKI Beta
Resource Certification
The Resource Certification project establishes a public key infrastructure (PKI) commonly known as RPKI (Resource Public Key Infrastructure) that combines the hierarchy of the Internet resource assignment model through Regional Registries (RIRs) or National Registries and the use of digital certificates based on the X509 standard. In general, X509 certificates are typically used for authentication either of an individual or, for example, a website. In our case, X509 certificates will not include identification information as their only purpose will be the transfer of the right to use Internet resources. Read More
What is a Beta Version?
Within the software development cycle, after having implemented critical functionalities, developers wish to make the application available to end-users. The application that is presented to the user already has most of the desired capabilities, yet there still may be some data display or internal process faults. Such applications are known as 'Beta Versions'. The main benefits of releasing this system are the possibility of obtaining feedback from end-users, as well as fault detection and reporting. Feedback on display or system logic improvements is specially appreciated and will be taken into consideration by the development team at this stage.
Resource Certification System Beta Version Release
The following application is the result of three years of design and planning plus one year of technical work, and it is the first time the LACNIC Resource Certification System is introduced to end-users. For this reason, we would like to invite you to interact as much as possible with the system, generating material, reporting faults, asking questions and/or suggesting improvements. By doing so, you will help us corroborate that what we have developed so far is working properly and create new functions, while bringing the system closer to meeting the needs of actual users. This Beta Version is intended for users that are members of LACNIC and appear as an organization's Administrative Contact or Technical Contact of an entity that has IP addresses blocks. The type of actions that users are allowed to perform depend on their role.
Resource Certification System Features and Functions
Features or functions common to both types of users
- Login with registry system username and password
- Multilanguage
- Help
- Component descriptions
- Contextual help
- General system description
Associated to organization’s admin.
- See AC or organization details
- Generate, change password, revoke and download certificate.
- See organization’s IPs and ASNs
- See performed actions associated to the AC
Associated to the blocks' technical contact
- Generate, Edit, Validate and Download ROAs
- See Authorized Resources
For more information on how to perform actions and conceptual and/or technical details of the generated cryptographic material, please login into the Resource Certification System Beta Version at: http://rpki.lacnic.net/rpki/ and see the application's Help section.
Technical recommendations
The application has been tested and runs well on the following browsers:
Internet Explorer, version 8 or higer
Mozilla FireFox version 3.0 or higer
Google Chrome version 4.1 or higer
The use of the browser's "Back" button is not recommended, as outdated information may be displayed.
The page contains JavaScript.
Ideal display resolution 1024p x 768p.
Did you find any errors? Do you have any suggestions?
It is safe to say that error detection and user familiarization with the application represent 90% of the purpose of releasing the software in Beta Version. Therefore, if you have detected an error or would like a specific new feature, please contact our development team by phone or by e-mail.
Phone: (+598) 2 6042222 ext 4126
E-mail: rpki-admin@lacnic.net
Launch
LACNIC has set October 1, 2010 as the tentative release date for the Betav2 Version. Despite this, because of this Beta Version's particular features, the application may suffer scheduled downtime.
|