This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] [ncc-services-wg] Implementation of Resource Certification (RPKI) for PI End User Resources
- Previous message (by thread): [routing-wg] Implementation of Resource Certification (RPKI) for PI End User Resources
- Next message (by thread): [routing-wg] [ncc-services-wg] Implementation of Resource Certification (RPKI) for PI End User Resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jac Kloots
Jac.Kloots at surfnet.nl
Tue Oct 22 11:06:03 CEST 2013
Alex, On Tue, 22 Oct 2013, Alex Band wrote: > The issue is: A PI End user must prove to the RIPE NCC that they truly are > the legitimate holder of the resources they would like to have a > certificate for. What proof do they need to give to the RIPE NCC before we > grant them access to the system? Not having followed all of this discussion, but isn't there an effort going on as result of RIPE-452 (http://www.ripe.net/ripe/docs/ripe-452) for having a contractual relationship between PI end-users and the RIPE-NCC. Isn't this contractual relationship the best proof for being the legitimate holder of the PI resource? Jac -- Jac Kloots Network Services SURFnet bv
- Previous message (by thread): [routing-wg] Implementation of Resource Certification (RPKI) for PI End User Resources
- Next message (by thread): [routing-wg] [ncc-services-wg] Implementation of Resource Certification (RPKI) for PI End User Resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]