
Hi, On Thu, Mar 14, 2013 at 12:41:33PM +0100, Andrew de la Haye wrote:
2) A PI End User requests a resource certificate through their sponsoring LIR and gets access to the ROA management system themselves, or delegates management to the sponsoring LIR
3) A PI End User requests a resource certificate directly from the RIPE NCC, without becoming a member, and obtains access to the ROA management system
Supporting both 2) and 3) seem to make sense to me. To avoid creating a high workload, 3) would need to be done in a mostly automated fashion - similar to what is happening today: if the sponsoring LIR sets up a mntner object that permits the end user to create their own route:/route6: objects, the end user can create "old-style" route authorization without involving the NCC. Something like this, sort of "between 2) and 3)" - the sponsoring LIR creating an access code of some sorts, and the end user using that to talk to the NCC systems. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279