You're looking at an older version: 3
The current (published) version is 4This proposal lays out guidelines for how LIRs can receive Resource Public Key Infrastructure (RPKI) certificates over their Provider Aggregatable (PA) address space holdings and how these certificates should be maintained.
a. New
Following guidelines are to apply only for certification of Provider Aggregatable (PA) address space allocations that are held by the RIPE NCC members in good standing.
The RIPE NCC will issue certificates upon request for RIPE NCC supplied Provider Aggregatable (PA) address space allocations to the LIR that is the registered holder of that space.
The certificate will be issued via a secure channel.
Certificates will be issued with a validity period of up to 18 months or as otherwise stated in the RIPE NCC Certificate Practice Statement.
In the event of revocation due to security breach or similar, new certificates will be issued with a validity period equal to the remaining validity of the revoked certificate.
Certificates will at all times reflect the registration status of the resource.
The RIPE Certification Task Force (CA-TF) was formed at RIPE 53 to advise, review and to provide feedback about a certification system. More details about the CA-TF can be found at:
http://www.ripe.net/ripe/groups/tf/certification
Since RIPE 53, the CA-TF has been looking at the system from several angles such as benefits and usefulness of it as well as operational, business and policy implications that it may bring. As these issues were narrowed down for discussion, CA-TF has reported to the community at regular intervals.
This proposal is a product of the work done by the CA-TF. The task force has studied possible policy implications and decided that a short initial policy will be useful that will be a guideline for a certification system for the RIPE community to discuss.
At this stage, a policy only for LIRs holding PA address space is proposed. The CA-TF believes that the system should cover PA resources initially, as this is the simplest case for the system. Once a policy for PA resources for LIRs has been discussed and the community has agreed on guidelines, then the CA-TF will consider more complicated scenarios, such as PI address space and ERX and legacy address space. This phased development is also inline with the technical implementation of the system, as certificates for PA allocations are the first real cases for the certification system. Certification of other resources will be implemented later on.
It is proposed that the validity of certificates is tied to the registration status of the resource. Rules and processes for deregistration of resources by the RIPE NCC are being clarified by a new draft document from RIPE NCC “Draft: Closure of LIR and Deregistration of Internet number resource” presented at RIPE 61 Services WG:
http://www.ripe.net/lir-services/ncc/legal/ClosureofLIRandderegistrationofINRs_finaldraft.pdf
None.
Note: In order to provide additional information related to the proposal, details of an impact analysis carried out by the RIPE NCC are documented below. The projections presented in this analysis are based on existing data and should be viewed only as an indication of the possible impact that the policy might have if the proposal is accepted and implemented.
This proposal directs the RIPE NCC to supply to its members, upon request, a certificate for their IPv4 PA Allocations.
This proposal only applies to IPv4 ALLOCATED PA blocks that were issued by the RIPE NCC and excludes early registration and legacy space, as well as blocks marked as ALLOCATED UNSPECIFIED or ALLOCATED PI.
Also excluded are other types or resources, such as IPv6 and AS numbers.
If resources are returned to or reclaimed by the RIPE NCC, any certificates issued for them will be revoked when the relevant objects are deleted from the RIPE DB.
Address/Internet Number Resource Consumption:
After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented.
Fragmentation/Aggregation:
After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented
Registration Services:
The internal procedures for implementing this policy have not been finalised yet. It is therefore not possible to assess the precise impact that this will have on the Registration Services Operations. As certification is not mandatory for RIPE NCC members, it is not possible to accurately predict the workload increase for the RIPE NCC.
Billing/Finance Department:
After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented.
RIPE Database:
After analysing the data that is currently available, the RIPE NCC does not anticipate that any significant impact will be caused if this proposal is implemented.
After analysing the data that is currently available, the RIPE NCC does not anticipate that the implementation of this proposed policy will cause any significant legal implications.
However for clarification purposes the following points should be emphasised:
1. Legal framework considerations
The legal framework around this service is in line with existing policies and procedures regarding registration. Please note that the details of the service are outlined in:
2. Law Enforcement Agencies’ intervention
According to the existing legal framework the possibilities for LEAs to order revocation of certificates are extremely limited. Given that certificates reflect the registration status of the resources, for a certificate to be revoked the resources must be deregistered. The introduction of certificates as such does not have any additional impact on the level of possible LEA intervention.