Hello APWG, (copying in NCC services WG, but since this is more regarding the formal policy proposal side of things, the place to discuss it is the apwg list -> reply-To: has been set accordingly). We have a slightly weird situation here where we have a policy proposal (2008-08) that has not *yet* concluded, which give the RIPE NCC the mandate to setup and operate the infrastructure to give out certificates to LIRs from the RIPE region (PA space holders, for a start, PI to be done in the next round). This proposal has not yet concluded, due to mostly "word smithing" reasons, and also due to somewhat lacking feedback from the community (that's *you*). There was no strong resistance either, so I assume that it might eventually reach consensus. On the other hand, the RIPE NCC sees the necessity for this sort of machinery, and has started the service *already* (see below for the mail from Alex Band with the NCC view of things), without waiting for the proposal to conclude. The RIPE NCC members have approved the expenses for this as part of the NCC business plan, so the NCC has the necessary (at least financial) backing to go forward here. So, technically, we might question whether we need the policy proposal 2008-08 at all anymore, or whether it should be withdrawn (being obsoleted by events). I have discussed this with the certification task force (CA-TF) and Alex' mail also answers this - the NCC wants a clear policy document that says that not only the financial side is OK, but also that the address policy community agrees with what the NCC is doing, and gives their support to the NCC. As a consequence, you'll see 2008-08 v3.0 show up here soon, for another round of review, and I *really* would appreciate a somewhat more active feedback from the WG (you!) this time. regards, Gert Doering, APWG chair On Mon, Jan 31, 2011 at 09:30:25AM +0100, Alex Band wrote:
Dear colleagues,
It's been one month since I sent the announcement about the RIPE NCC Resource Certification service. I would like to give you an overview of the current status.
The facts by numbers: ------------------------------ LIRs who have enabled the service: 219 Number of Route Origin Authorisations they created: 170 Number of prefixes covered by these ROAs: 469 Total IPv4 space covered by ROAs in the RIPE region: 40159 /24s Total IPv6 space covered by ROAs in the RIPE region: 7340035 /48s Unique visitors to ripe.net/certification: 1564 Downloads of the RIPE NCC Validator: 117
So while 219 LIRs have enabled the service, and very diligently created a large number of ROAs to specify their routing policy, unfortunately nobody gave any feedback on any of the mailing lists. It is very important that you let your voice be heard and provide input on policy proposal 2008-08: http://ripe.net/ripe/policies/proposals/2008-08.html
Please note that version 3.0 of this proposal will be published very soon. As soon as it is available, I urge you to read it and provide feedback, because the fact that the current service not backed by a policy is not a sustainable state of affairs.
Kind regards,
Alex Band Product Manager, RIPE NCC http://ripe.net/certification
P.S. Here are some links courtesy of LACNIC in case you would like to track the progress: http://www.labs.lacnic.net/~rpki/rpki-monitor/rpki-ta-status.xml http://www.labs.lacnic.net/~rpki/rpki-evolution-report_EN.txt http://www.labs.lacnic.net/~rpki/rpki-heatmaps/latest/ripe-roa-heatmap.png
Gert Doering -- NetMaster -- did you enable 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