[ncc-services-wg] [ncc-announce] [news] RPKI and PI End Users Proposal - Feedback Requested

On 11/02/2013 15:07, Sascha Luck wrote:
> I thought the decision at the time was that the provision of rpki
> services was independent of, rsp. not subject to, policy?

The RIPE NCC originally provided RPKI services under the terms of the
Certification Task Force;  these terms were explicitly outlined in the text
of the ill-fated 2008-08, which stated in the explanation part:

> Once a policy for resources held by LIRs has been discussed and the
> community has agreed on guidelines, then the CA-TF will consider more
> complicated scenarios, such as PI address space and ERX and legacy
> address space. This phased development is also inline with the technical
> implementation of the system, as certificates for LIR resource holders
> are the first real cases for the certification system. Certification of
> other resources will be implemented later on.

While the proposal failed to achieve consensus, this sentence did specify
the terms of reference for the RIPE NCC's engagement for providing RPKI
services at the time and it was clear that it excluded PI / ERX address blocks.

There were two proposals at the November 2011 General Meeting to change the
RIPE NCC's mandate: Option A was to instruct the board to drop RPKI
completely and Option B was to continue RPKI development, but without ROAs.
 Neither proposal received enough support to be adopted, so the board
assumed a mandate to continue with the existing arrangements:

> If neither resolution is adopted, the RIPE NCC will continue the current
> Certification/RPKI activities of the association.

(http://www.ripe.net/lir-services/ncc/gm/november-2011/agenda)

My reading of this is that if the board wants to proceed with RPKI for PI
holders - and later, ERX holders - it will need a mandate from the RIPE
Community and probably also the RIPE NCC membership.

Nick