This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] Use of the Reserved IP Pool
- Previous message (by thread): [address-policy-wg] Use of the Reserved IP Pool
- Next message (by thread): [address-policy-wg] Use of the Reserved IP Pool
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Baeza (Red y Sistemas TVT)
d.baeza at tvt-datos.es
Fri Jul 4 17:00:54 CEST 2014
Hi, El 04/07/2014 13:53, Gert Doering escribió: > How can RIPE NCC IPRAs verify that these requirements are met? > > How can you prevent abuse? (Like, "all 1024 addresse must respond to > ping!" - that's more easily achieved by faking it than if you connect > real customers that have firewalls...) > > Rulese need to be a) easily verifable for someone not at your network, > and b) not so easy to just circumvent. > Is that the only problem? Was hoping more... :) How was it done before? How ppl used to prove they needed more space? -Daniel
- Previous message (by thread): [address-policy-wg] Use of the Reserved IP Pool
- Next message (by thread): [address-policy-wg] Use of the Reserved IP Pool
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]