[address-policy-wg] 2008-08 (Initial Certification Policy in the RIPE NCC Service Region) going to Last Call
- Previous message (by thread): [address-policy-wg] 2008-08 (Initial Certification Policy in the RIPE NCC Service Region) going to Last Call
- Next message (by thread): [address-policy-wg] 2008-08 (Initial Certification Policy in the RIPE NCC Service Region) going to Last Call
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Martin Millnert
millnert at gmail.com
Tue May 3 18:29:54 CEST 2011
James, Erik, On Tue, May 3, 2011 at 10:59 AM, boggits <boggits at gmail.com> wrote: > On 3 May 2011 15:42, Erik Bais <ebais at a2b-internet.com> wrote: >> Hi James & Malcolm, <snip> >> I will however use the repository to check if what my customers want to >> start to announce to our network. And when PI is going to be accepted after >> this policy, also PI. > > This a useful function of the RPKI (and the use that I expected this > for, when it moves to automation then I have the fear. This is essentially not a property of RPKI however. It is a property of the RIPE DB itself. Let me quickly illustrate: To check what your customers wants to announce to you -- you talk to *them*. To check if what the customers wants to announce is also listed in $IRROFCHOICE, you check $IRROFCHOICE. I don't see what problem RPKI solves here. Kind Regards, Martin
- Previous message (by thread): [address-policy-wg] 2008-08 (Initial Certification Policy in the RIPE NCC Service Region) going to Last Call
- Next message (by thread): [address-policy-wg] 2008-08 (Initial Certification Policy in the RIPE NCC Service Region) going to Last Call
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]