[address-policy-wg] [ncc-services-wg] Resource Certification for non-RIPE NCC Members
- Previous message (by thread): [address-policy-wg] [ncc-services-wg] Resource Certification for non-RIPE NCC Members
- Next message (by thread): [address-policy-wg] [ncc-services-wg] Resource Certification for non-RIPE NCC Members
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dan Luedtke
maildanrl at gmail.com
Mon Jun 10 10:24:52 CEST 2013
> 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) As a PI holder and a router operator I support this proposal. I want others be able to verify my prefixes. RPKI, if used widely, can be a much more acurate source for routing information than the databases are. Even in RIPE region, where the database tends to be well maintained. The more resource holders are allowed to use RPKI, the better. I would even pay a fee for the signing process of my resources, just in case this is about money.
- Previous message (by thread): [address-policy-wg] [ncc-services-wg] Resource Certification for non-RIPE NCC Members
- Next message (by thread): [address-policy-wg] [ncc-services-wg] Resource Certification for non-RIPE NCC Members
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]