[ncc-services-wg] Resource Certification for non-RIPE NCC Members

Hi,

On Mon, Jun 03, 2013 at 02:08:46PM +0200, Erik Bais wrote:
> As you may have seen, I’ve created a policy proposal to ask the RIPE NCC to
> allow Resource Certification for non-RIPE NCC member resource holders. (IXP
> / Legacy space and PI space holders)  

Speaking as a router operator, I support this proposal.

For services offered by the RIPE NCC, the history and colour of an IP
prefix should not make a difference - so "PA", "PI" or "legacy" prefixes
should be treated all the same.

(If the community decides to abandon RPKI because of whatever reason,
fine with me - but as long as the paying members have voted to keep the
RPKI system running, it needs to work for all prefixes that the RIPE
NCC feels authoritative to state "this person is entitled to decide 
who gets to route the prefix" - i.e. verified contract holders, LIRs,
etc)

Gert Doering
        -- internet operator
-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 306 bytes
Desc: not available
URL: <https://lists.ripe.net/ripe/mail/archives/ncc-services-wg/attachments/20130603/aceae01f/attachment.sig>