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/ncc-services-wg@ripe.net/
[ncc-services-wg] [coms] Certifying of PI End User Address Space
- Previous message (by thread): [ncc-services-wg] [coms] Certifying of PI End User Address Space
- Next message (by thread): [ncc-services-wg] [coms] Certifying of PI End User Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Fearghas McKay
fearghas at gmail.com
Mon Mar 18 15:50:30 CET 2013
Andrew On 18 Mar 2013, at 14:44, Andrew de la Haye <ripencc-management at ripe.net> wrote: > To answer your first question, option 3 would require more resources than option 1 because it would require the RIPE NCC to create new processes for handling non-members. The NCC already sure has a large number of people in the dB who are non-members ? Some of whom will hold resources as well as being contacts ? Is the use case so drastically different ? Regards Fearghas
- Previous message (by thread): [ncc-services-wg] [coms] Certifying of PI End User Address Space
- Next message (by thread): [ncc-services-wg] [coms] Certifying of PI End User Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]