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] [ncc-services-wg] Implementation of Resource Certification (RPKI) for PI End User Resources
- Next message (by thread): [routing-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alex Band
alexb at ripe.net
Wed Oct 23 15:24:22 CEST 2013
On 23 Oct 2013, at 12:41, Nick Hilliard <nick at netability.ie> wrote: > On 22/10/2013 19:55, Alex Band wrote: >> 4: The PI End User must enter the RIPE Database MNTNER password/key(s) for >> the inetnum objects of the resources, to prove they have authoritative >> control over them > > you're assuming that the end user maintains their objects. This is not > always going to be the case. I'm not assuming that at all. If the sponsoring LIR manages the RIPE DB objects on behalf of the PI End User, they will be able to authenticate against the inetnum and perform these steps. -Alex
- Previous message (by thread): [routing-wg] [ncc-services-wg] Implementation of Resource Certification (RPKI) for PI End User Resources
- Next message (by thread): [routing-wg] Need for "import-via:" and "export-via:" attributes in AUT-NUM object
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]