resource quality assurance in lacnic arturo l. servin apnic 31
TRANSCRIPT
Resource Quality Assurance in LACNIC
Arturo L. ServinAPNIC 31
Why
• Addresses are not guaranteed to be routable, but:– We want a good “product”
• As IPv4 space becomes scarce:– Illegal use of space– Requirement to use returned/recovered space (which
may be not clean)
Resource Quality Assurance in LACNIC
• Historically we applied some basic RQA to our address
• In 2010 we started to give some shape and formality to a new RQA process
• Today we have internal processes and we plan to publically announce this effort and some results soon
The process
Resource Tests
Rank
Allocate
Corrective actions
Rank > Threshold
Yes
No
Identifying quality of resources
• Is it registered by some one else?• Is it announced by some one else?• Is it reachable?• Is it “dirty”?• Does it get background traffic?, How much?
The tools
• Whois (RIRs, IRRs)• RIPE NCC RIS (Routing Information Service)• Looking glasses and route-servers• De-Bogonising New Address Blocks• RADb• Merit’s Darknet Analysis Project• Reputation services for IP addresses
Next steps
• Publically announce our efforts to our community• Enhance process with experience– i.e. better values for thresholds– Tools for internal support– Automatize some activities
