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/[email protected]/
[ncc-services-wg] Implementation of Resource Certification (RPKI) for PI End User Resources
- Previous message (by thread): [ncc-services-wg] Implementation of Resource Certification (RPKI) for PI End User Resources
- Next message (by thread): [ncc-services-wg] Implementation of Resource Certification (RPKI) for PI End User Resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at netability.ie
Wed Oct 23 11:00:08 CEST 2013
On 22/10/2013 16:12, 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? there's no way of necessarily knowing that the contact info in the ripe database is correct, even if the resources are correctly registered to the legal person described in the organisation object. This means that the RIPE NCC has no real way of knowing if J. Random end user is the correct contact for the PI resource, which means that it needs to devolve the initial stage of this authorisation to the sponsoring LIR. This probably sucks. Nick
- Previous message (by thread): [ncc-services-wg] Implementation of Resource Certification (RPKI) for PI End User Resources
- Next message (by thread): [ncc-services-wg] Implementation of Resource Certification (RPKI) for PI End User Resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]