[ncc-services-wg] 2013-04 New Policy Proposal (Resource Certification for non-RIPE NCC Members)
- Previous message (by thread): [ncc-services-wg] 2013-04 New Policy Proposal (Resource Certification for non-RIPE NCC Members)
- Next message (by thread): [ncc-services-wg] 2013-04 New Policy Proposal (Resource Certification for non-RIPE NCC Members)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Mon May 20 18:27:39 CEST 2013
Hi, On Mon, May 20, 2013 at 04:31:47PM +0100, Dave Wilson wrote: > > http://www.ripe.net/ripe/mail/archives/address-policy-wg/2011-May/005737.html > > I still don't understand how what this message describes is a > change. The concerns also apply to the status quo. I have to use a > central database in order to get my prefixes routed by my upstreams. Indeed. The main change RPKI brings is that you can store a local copy of the database *and validate that local copy* against unauthorized tampering (in-transit or local). If the black helicopters force the RIPE NCC to remove a route6: object, the (former) owner of this object will have issues with his prefix as well... 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 -------------- 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/20130520/d478570b/attachment.sig>
- Previous message (by thread): [ncc-services-wg] 2013-04 New Policy Proposal (Resource Certification for non-RIPE NCC Members)
- Next message (by thread): [ncc-services-wg] 2013-04 New Policy Proposal (Resource Certification for non-RIPE NCC Members)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]